New
#450
Ian --want to say thank you to you that your message #444 about how to copy one of the system file -- volsnap.sys I have followed your instructions and to my surprise that volsnap.sys file not found. Oh oh now I am not sure what else to fix because I can't get into Windows after login. Any idea how to get around to get this file install from somewhere online or on Windows 10 Pro disk or any other solution to get that fix. I can't get into my desktop now and don't want to reinstall them because of one sys file.
Looking forward to hear about this if you have better answer.
John
volsnap.sys 17004 x64 Pro
Can anyone help to PM me this file, I lost Windows.old after disk cleanup
Edit:
Did anyone try to replace this file from 16299.19? Will it work?
Should work as whilst I was troubleshooting my issues as described in my post #444, both fixes also worked with 16296 (an earlier build than your 16299). Architecture must be the same though i.e. must be the same 64/64 or 32/32 not 64/32. I would PM/link my dropbox versions but I've not enough postings on this site to allow PM's. You can always extract from 16296 downloaded from here:
https://www.microsoft.com/en-us/soft...reviewadvanced
imcanadian / John
The above is one way forward you could try but if you can't find/don't have volsnap.sys in the locations I pointed you to, then I am at a loss I'm afraid. Hopefully someone with enough postings on here will PM it to you?
Ian
FCU updated successfully on my ASUS T100ATF 2in1 lappy from WU. It took almost 4 hours but considering it's life started with W8.1, has 2GB RAM and 32GB eMMc memory, I think it did fairly well. Everything seems to be working just fine.
I've got about 12 USB3.0 drives that I use for several different things. They are all between one and four TB's, and I ONLY use WD drives. I've never had a problem with any of them. And I started the windows insider program in the first few weeks it was available. So I'm not so sure I'd agree with that statement.
I do agree with one of the earlier posters who thought it was line specific. I believe from what I have read, that the Skippy line has many mistakes in it, and the development line is much more refined, and thus has many fewer problems.
OK, five days of fighting and I finally gave up.
A recap:
Got a refurbished Asus laptop on Friday evening. Restored a 17004 Macrium image, everything OK. Just an hour after restoring the image, 17017 was released. Upgrade 17004 to 17017 went smoothly although it took some time.
After the upgrade, I got a GSOD an hour after boot, then again a GSOD an hour after reboot:
Tweet
— Twitter API (@user) View on Twitter
After some more GSODs, each 60 to 65 minutes after boot, I gave up and tried clean installing 17017. The same continued, cldflt.sys causing a GSOD always 60 to 65 minutes after boot.
Tried to take cldflt.sys from 17004, replacing the one in 17017 with it. No more GSODs but otherwise I pretty much bricked the laptop. OneDrive, all Office applications and Microsoft apps stopped working:
Tweet
— Twitter API (@user) View on Twitter
Decided to restore 17004 image and skip 17017, but only an hour after doing it, I just couldn't let it go and started testing. In past few days I've only been clean installing, upgrading, restoring an image and so on. I've tested all possible scenarios I could think of:
- Upgrade 17004 to 17017
- Clean install 17017
- Clean install 15063, upgrade to 17017
- Run SFC and DISM countless times trying to repair Windows
Whatever I do, whatever scenario to get 17017, I will get GSOD 60 to 65 minutes after boot, never less than 60 minutes never more than 65 minutes. Like a clockwork. Faulting driver every time cldflt.sys. Laptop works perfectly, Windows has no issues, then an hour after boot, a GSOD.
Tweet
— Twitter API (@user) View on Twitter
There's a limit in how much you can continue testing. At least I have this limit and I reached it today. I will totally forget 17017 and hope this issue is not present in next builds.
I made a new 17004 deployment image this afternoon and finally now, almost midnight on Wednesday I am in peace (and in pieces!). I have a fine tuned 17004 up and running in satisfying way, I have totally forgotten 17017.
Kari