Announcing Windows 10 Insider Fast+Skip Ahead Build 17035 for PC Insider

CountMike · 09 Nov 2017

magilla said:

27 hours later and MSFT hasn’t been able to restore availability to large AMD customer base. I find that really interesting, yet annoying

If it was something simple they would have delayed it day or two. I'm afraid it's something major.

f14tomcat · 09 Nov 2017

linw said:

I don't have any problem with couple of issues reported by others.

One Drive opens normally from Chrome and windows.old deleted fine with disk cleanup.

@linw

It's the one in the taskbar, not Online or Store App....they are fine.

Announcing Windows 10 Insider Fast+Skip Ahead Build 17035 for PC-2017-11-09_15h59_06.png

cereberus · 09 Nov 2017

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.

linw · 09 Nov 2017

Sorry, f1, missed that point. Don't have a taskbar icon.

magilla · 09 Nov 2017

cereberus said:

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.

Thank you for your feedback. And your bravery going where most of us were afraid to go.

larc919 · 09 Nov 2017

doriandiaconu said:

It seems that both this update and the old one made it unable to remove the Windows.old folder through disk cleanup.

Now I got 2 Windows.old folders. Any help on how can I delete them?

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.

Tony K · 09 Nov 2017

larc919 said:

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.

Thanks for that.

I ran dir c: and it lists everything in alphabetical order. So then if .old is still there it would be listed in the W's as windows.old?

martyfelker · 09 Nov 2017

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)

martyfelker · 09 Nov 2017

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

LEOPEVA64 · 09 Nov 2017

martyfelker said:

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)

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.