Yes build over build, until now every time this process was successful, but this tim it failed for 10122.
No problem...I'm the opposite...haven't bought Intel at home since '99. AMD has pretty much always beaten Intel in the performance-per-dollar category, imo... I meant to ask as well, how many years has it been since you bought an AMD cpu? I ask because your comments about "super hot" are amusing and really haven't applied for many years...the 4GHz+ desktop 6 & 8-core AMD cpus I've used at home for the last 3.5 years both TDP @ 95W, and use considerably less than that when web-browsing, etc. The stock heatsinks are all I need and they're very scrawny. OTOH, I've seen some gigantasaurus heat sinks for i7's...
Congrats to all geeks over here, today is Geek Pride Day! Star Wars fans, The Hitchhiker's Guide to the Galaxy fans and Terry Pratchett's Discworld fans too Oh, forgot Memorial Day, but that's not a "happy" day to celebrate Maybe "reverent", "solemn" or "grateful" but not "happy".
I can't seem to get any of the links in this thread for 10122.0.150513-1845.fbl_impressive_clientpro_ret_x64fre_en-us to work. I get an access denied error. I am hesitant to download a premade ISO because of the possibility of tampering. My research indicated that Windows Update creates Install.esd in C:\$Windows.~BT\Sources but the SHA-1 hash for this file (as computed by 7-zip and FCIV) is not 91ccec37df726d9306591d8f7fc0137c9bddf3bc as posted in this thread. Is that normal? I have deleted Install.esd to force Windows Update to download it again, but the hash is still wrong. I get error 0x80004005 when Windows Update tries to install the new build, and I have had no luck troubleshooting, so I thought I'd just make an ISO for a clean install. But I don't want to try that if I have a bad ESD image.
install.esd is a decrypted file, will always has different hash, and can be used exactly like original encrypted esd
How to remove the folders in "This PC"? Until Build 10074, a Regfile to remove the folders (used previously in Windows 8 and 8.1) worked fine, but since Build 10122 and now with Build 10125 it doesn´t work anymore.