Hello everyone I was in search for a WIN7, pre Telemetry ISO (before june 2015) since online i can't find an untouched ISO, i download one, directly from MS server (using the ISO Downloader tool by Heidoc) The ISO date of last modify, was "4 December 2011 14:27" Evrything was ok, except for the fact that. After installation, no internet no update, under service i found some unexpected voice: Diagnostics Tracking Service, dmwappushsvc etc I don't understand, was a 2011 version...this telemetry stuff come with patchs after 2015!? How is possible? since the last modification dates back to 2011? Maybe i'm wrong? is not a 2011 version? Some info about this ISO: BUILD: 7601.17514.101119-1850_x64fre_client_it-it_OEM_Ultimate- Windows 7 SP1 Build 7601.17514.101119-1850 GSP1RMCULXFREO_IT_DVD Win7_Ult_SP1_Italian_COEM_x64.iso checksum: CRC-32: F384A9DC MD5: EA3AF9072E271489AD7AFFCCC640A6AD SHA-1: E0AFBBFF783A8FD66AD3AB1F98AA59BB4D592B22 SHA-256: 68C2767C728C38E5DBF8F3E4BCE841D734C9FA7F23F763EC3589E998F9B90560 P.S. If anyone could tell me where to get an untouched "pre telemetry" ISO that has an official verifiable checksum, I would be grateful. Because my last alternative is this: CRC-32: 06B4258E MD5: B00D1EABC043412FD9CD13F6FE04202D SHA-1: 9F92DF8607D7C67FB19BB92910A8AE74A584D22E SHA-256: 3B3C5F93390EBAC8099090F74891B112E79F68D6C41B1714C3C8426DAAE85E8C But i'm not sure is an untouched version, because i can't find an official MS checksum to check.
When in doubt, always open the ISO and look for the date of the .\sources\install.esd or .\sources\install.wim file. Usually, a serviced homebrew ISO does only touch this file (where the whole beef is stored).
Thanks guys for the answers. @shhnedo Tnx for the search done. I downloaded from The Eye in the past, i trust this source at 60%, but for an OS... I have to trust at 100%, and since SHA-1 has been compromised...dunno. @Carlos Detweiller Thanks for the info! About the file "install.wim" it was last edited in 2011 !?!?!?!?! From what i can see ther's no files beyond 2011...this version it should not have any signs of telemetry. I can't get over it.. I could keep this version, and proceed slowly to remove all the crap, injected by MS, but since it should be a pre telemetry version, and i find inside signs of tampering by MS, I wonder... how much will have messed up? Someone know where find an official MS checksum, of every Win7 build, in sha 256 or 512?
WoW, thanks! Very kind from you @Enthousiast for having generate me a link. I'll try it, and i let you know, if MS has injected other unwanted patch, even in this one. This should be uploaded last time 12/15/2014, so no telemetry, i hope. -Great tool! -I wish i had found MDL before, is great, i received a lot of info.
There are now newer officially, by msft, released windows 7 ISO's, the one you get is the most recent one (2011).
It's not what "telemetry" sends to MS, my concern. I care that lot of process don't maintain busy my PC with "useless" stuff. As many additions since 2015 do, putting stress on the machine, and drives, with unnecessary work, and continuous errors. Since i need to install the OS several times. I simply want a, much as possible clean OS. With less stuff preinstalled, that i don't have to modify everytime via service/prompt/regedit "loosing my time". It's better, the absence of a function, rather than its modification, which is likely to create conflicts, and errors. Less useless stuff = more efficiency and time to dedicate to what really matters.
Not installing updates will cause more problems than the use of 1MB more or less resources. Create one iso with all your desired preconfigurations and use it for all installations. The so-called "telemetry" on win 7 is not to be compared to what it is on 8.1/10. You can safely update the clean iso, using simplix, it excludes all telemetry inserted by updates, removes cpu restrictions for win 7 updating, it can install nvme updates and has an option to install an USB3.x driver installation tool, which installs the appropriate usb3.x drivers during windows installation. You also can do a VM install in audit mode and preconfigure your windows, install stuff like dx9c or dotnetfx472, etcetc, and sysprep/capture the install to an install.wim and use the install.wim/iso to install on your systems.
It's recent. Happens when installing the latest Monthly Rollup. All I'm saying is that with Windows 7 you usually have to exercise some caution when installing updates, because they have a tendency to break some functionality... that's all.
I recently created 3 AIO iso's of windows 7 SP1 with all updates pre-integrated and no problems occured when i installed all 66 indices i created, on real hardware on a VM. But do whatever you want, but don't only talk by googling (many posts out there are from copy/pasters, windows bashers, or as we see often here lately, clueless choppers, etcetc...) but by own experiences. Personally i would rather risk a rare bug when updating compared to what ransomware can cause
I didn't Google, this comes from a respected website that I usually consult to see if I may encounter issues with updates. I will admit most of the issues recent updates raise don't affect me, but it's always nice to be aware. Once again, I didn't advocate not to install updates, just that people do have legitimate reasons to be doubtful of recent updates. But I won't dwell on the subject anymore, as I may be derailing the thread a bit...