Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC Insider

Another thing you can try is getting a virgin cldflt file from your -wim install media(it has to be wim and NOT ESD)

Mount the media, go to the install wim folder in sources(make sure you go to the correct index) open install wim with 7Zip,
G:\sources\install.wim\Windows\System32\drivers\
copy it to desktop, then from there you can replace it in your system's system32 drivers folder

swarfega said:

It says above it that you are on Pro. Not sure what /EA means.

Yes, I am on Pro. But that /EA no idea either.
Thanks

cereberus said:

AFAIK /EA mean Enterprise Agreement (not Enterprise Edition).

Run showkeyplus, click on keys to hide them and post image.

Thanks for the explanation!
I haven't that image installed on my computer, that was the reason of my question because
as I can't install from Windows Update I'll be trying to install it from an ISO.

If I install that do I still get the normal Pro version without any Enterprise related OS?

Cliff S said:

Have you tried Shawn's tool>: Add Take Ownership to Context Menu in Windows 10 User Accounts Tutorials

Thanks Cliff. And thanks Shawn. I took ownership via this program. However, after placing a different version of volsnap.sys in the \system32\drivers\ directory the system failed to boot and MS repair could not repair the drive. I rebooted from Macrium and restored the drive with the issue and it is bootable. Just not upgradable. Guess it will stay on Skippy 17004 until something else comes along that works. I have two other systems to play with so this one will just have to be!

Aspley said:

I also had this volsnap.sys error, I say had because I booted from the previous version recovery usb stick, went to the command prompt and copied the volsnap.sys to the c drive, actually to both locations, \system32\drivers and \SysWOW64, then rebooted

all OK at this time

So, you interrupted install (after first restart), booted to USB and perform copy? System files are not in their place at the time (or am I wrong here...)

Aspley said:

I also had this volsnap.sys error, I say had because I booted from the previous version recovery usb stick, went to the command prompt and copied the volsnap.sys to the c drive, actually to both locations, \system32\drivers and \SysWOW64, then rebooted

all OK at this time

Thanks for information and glad for you. I tried that and system wouldn't boot, giving me GREEN SCREEN greetings and then trying to repair, then saying it could not fix the problem.

Aspley said:

the install of 17017.1000 went as per normal, it ran for an hour or so no problems, but after a reboot it came up with the volsnap.sys error, I hadn't at that stage made a recovery stick, so that why I used an earlier version.

I have no choice to stop it, once the error occurs. It's a matter of seconds to boot back into 16299.

AndreTen said:

I have no choice to stop it, once the error occurs. It's a matter of seconds to boot back into 16299.

Same here - I am trying one more time. This time with Defender turned off Magic beans come next.
and the same crashing bluescreen saying too bad for you, sucker!