New
#80
Dona and her Insider Team made me SNAP to get this build. I never had any problem with the volsnap.sys on Build 17017 until I tried to update to this build. It would get to around 80% preparing to install then Green Screen. When the desktop restarted I would lose my network card. The only way to get it working again was to shutdown, pull the power cable push the power button then plug the cord back in and start the computer. I worked on it most of the night. Right now it's at 67% Installing. What I did to try and fix this was to replace volsnap.sys when a version from a earlier build. I mounted a Macrium image from a earlier build to copy the volsnap.sys from the C:\Windows\System32\Drivers folder. Then I went into the active C:\Windows\System32\Drivers folder and took Ownership (thanks @Brink for making it easy) of the volsnap.sys file and change the name. Then I copied the working volsnap.sys file into the drivers folder. Rebooted the computer and tried downloading again. So far no Green Screen and my fingers are crossed. :)
Install seemed a bit slow, but upgraded without incident.
Computer sleeps and it awakens but monitor won't wake up. This happened with 17017, also. Never been a problem before. Have latest driver for this video card and monitor is correctly configured. Seems like Josey Wales had this problem before --- or was it the opposite?
Thought i'd let defender do a full scan, could be a while
592621:27:18
cant wait for those last 18 seconds.
Roy
My desktop automagically started the upgrade before I got home yesterday, and completed it relatively quickly. When I first saw it it was at 3% installing after the first reboot (I assume) and it was done 10 minutes later.
And I was, again, as usual, able to make the ISO via UUP2ISO from the Windows.old directory. Seeing as I had no choice, since the update downlaoded and installed without any intervention on my part whatsoever while I was at work and then in transit home.
Of course, having a 1 TB SSD with the system and Program Files (Users tree moved to another SSD, and all special (storage) folders moved to mechanical drives) helps, in that I have gobs of space so Windows never runs out of storage space when updating. And, I have a laptop as a backup on which I can make the ISO if something ever does happen to Windows.old.
Time to play.
Interesting - I'm on the same log in after it completed the updates, even with the Notification to complete installing device drivers, and I unlocked and was able to drag my taskbar immediately.
Odd. I'll keep an eye out for that, though I usually never move my tb from its default position....
Lol...I have been so busy today that I haven't had the time to install this new build. ...tomorrow maybe... :)
I like that feature. Aero's little brother. They added it to Start screen tiles a few builds back as well. Not as noticeable there, though.
So far as I know it's been in Insider builds since early on.This is what I get when I click what's under the text.
I find it weird simply because I didn't have this writing before.
You mean right clicking the Start Flag? If so, that's the power user's context menu. Same as WinKey/X. Everything opens ok for me, Mike.
Don't remember that one, but C&Ped to my notes. Thanks.
Hmm. Interesting.
After updating both machines I see Skippy branch FULLY lives on. :)
Seems the last two versions 17017 and 17025 are incompatible with my machine
Neither version will install, both get stuck on windows logo on first reboot
Both on a never ending loop