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

slicendice said:

Updated both Fast Ring and Skip Ahead in Hyper-V. No issues to report on neither. Now for testing...

Those who has issues with Windows.old not getting removed after a full disc cleanup, PM me or Mention me here and I take a look. I had leftover folders on both VMs but I could remove all of them with my usual methods.

I got it deleted with no problems this time.

Everything appears to be working as it should, no faults found, Updating faultless yet again.....how annoying it must be for those with multiple problems to keep reading this.

Could it be that faults are minimised by having a separate SSD or HD specifically used ONLY for the Insider program.?
All programs, games, etc, can then all be loaded onto the O/S and tested.

It works for me.

dencal said:

Everything appears to be working as it should, no faults found, Updating faultless yet again.....how annoying it must be for those with multiple problems to keep reading this.

Could it be that faults are minimised by having a separate SSD or HD specifically used ONLY for the Insider program.?
All programs, games, etc, can then all be loaded onto the O/S and tested.

It works for me.

That's how I have it set, one disk each for W10, W7 and Mint with multiboot set in W10 and 7. Still I had some problems with some builds.

CountMike said:

That's how I have it set, one disk each for W10, W7 and Mint with multiboot set in W10 and 7. Still I had some problems with some builds.

I did state Mike "faults are minimised".....One cannot expect perfection with O/S,s in Beta.

During early stages of W10, encountered problems with W10 and W10 Insider multi-booting on same SSD, hence my preference of separation.

I believe it's first time I see with some pinned tiles/APPs, there's an option for Recent on right click, to open most recent files used with that APP.

I definitely think it would be prefereableto have a seperate drive for the W10 IP Builds and I'm hoping to get a spare 128GB SSD drive installed in my box in the future. But now I'll skip the harrowing tales of installation and just enjoy updating my Hyper-V VMs, including a Gen 2 Build 17040 which is proceeding swimingly. It's nice running W10 on a sperate partition at least. Since I can autologin one of the first things I do with a new clean install is run control userpasswords2 and remove my password.

Now the Hyper-V VM seems to be stuck at 54%. Could this be why there was this red exclamation point before the upgrade began? Has anybody seen this?

Winuser said:

I managed to get this build installed on my laptop and desktop. Took me over three hours. My laptop started out fast. It was almost to 100% and I was getting ready to make the ISO. As soon as it reached 100% it paused then started downloading again. The second download was slow. My green screen with the Memory Manager error still exist on the laptop and the desktop. The laptop green screens every time I do a shutdown or restart. The desktop green screens eveytime I do a shutdown.

I had something similar although mine was 2 complete installs (in the sense that could make 2 ISOs - the same exact byte count.