New
#150
My experiment with using an iso on a vm on amd pc failed - it got stuck with infinite waiting circles eventually. After a few hours I closed vm down and it reverted to 17025.
I use Windows install media (DVD or USB drive) to boot, then navigate to Command Prompt and run rmdir c:\windows.old /s . I don't use the /q switch because I like the security of knowing I haven't made a mistake and designated the wrong folder. After I run rmdir (or just rd), I run dir c: to make sure Windows.old is gone.
I find a stubborn Windows.old is often caused by something as simple as a single corrupt file. As long as that file exists in the system, Windows.old will keep refusing to get 100% deleted by usual means. You can often dig into the folder and find the problem area. The last time it happened to me, uninstalling and then re-installing a third party program fixed the recurring problem.
Will have to wait for the next update 17035 did not boot after setup.exe ran on any installation of 17025 including the physical disk. I'm glad of you could install but it appears to have several issues which is somewhat surprising. Try, try again (and you have upload 17036 to buildfeed.net)
The new build is a bust on all VMs and the physical machine. Won't but past the Windows 4 pane icon. Better luck next time
I see in the information that appears in "My computer" that one of your PCs has an AMD processor, if you are trying to install this build on that PC, you can't do it because Microsoft blocked the installation of this build on PCs with AMD processors, maybe you did not read the release notes in the first page, if that is not the case, please ignore my answer.