Update from 1607 to 1703 returns ...-Ox20017 error and Dism won't work 0x800f081f

[Wolfie]

BUT... 'winver' tell me I am now on Version 10.0 number 10240 !!!...

HI,

you should first start with a full system upgrade as you are a few versions behind!, I assume you used an older version of W10 to do your fresh install?:

https://www.windows10forums.com/threads/how-to-upgrade-windows-10-to-the-latest-version.13015/

 

[Saltgrass]

I will pass along my recent experience with my old Dell system.

I had not updated Win 10 on this system since Oct. 2016. The device did not show in my Microsoft account, so this may have effected what I saw.

I started with a machine which was working and running an older Build. Trying the normal update process to bring it up to the current install, looked like it was working OK but after two hours it had not gotten past 18% of downloading the updates, so I stopped the process. At this point the system's desktop was no longer performing normally.

After three attempts, I finally got the latest build to install from within Windows. The install completed but the system was very slow and the desktop icons, such as start button, were not functioning correctly. I could not log in to a Microsoft Account.. During this time I checked the Event Viewer and saw many messages (500 in one hour) about ESENT not being able to access the drive to write logs. The drive had over 100 GB free, so I did not understand such a comment in an error message.

After a second attempt to install over the current install I did a clean install (wiping the drive) and the install went normally. All updates are now installed and the Desktop icons are performing normally. My system is now showing on the Microsoft account since I was able to log on with my Microsoft account.

I suppose the bottom line, doing a clean install of the latest build will give you the best chance of a system working correctly.

 

[yvessr]

IMPOSSIBLE to install a fresh Windows 10 version from usb-Stick !

First I tried to upgrade my actual windows 10 to 1703 from within Windows, using a fresh downloaded MediaCreationTool > returning me a final error message 0x80070456-0xA0019...

Than I decided to install a fresh Win10 (on a reformatted C: partition) and therefore I burned a USB starting stick (also with MediaCreationTool and thus automatically set with an identical Win10 version as the one I am running) > problem when starting I got the Windows window with the 'spinning wheel' but after a few seconds it stopped spinnning and about one minute later my PC was turn down !
Then I made another USB stick (using Rufus) with a 'bootable' version of Win10 1703, but when trying to boot it I had exactly the same issue... stop and down !...

I really don't know at all what to do ?... how to get that USB really starting up and getting into the Win10 setup page...??? What can be the problem ???

Please HELP !

 

[Wolfie]

Might I suggest you download a copy of Gparted and use that to determine what exactly your partition layout looks like, you may have wiped the wrong partitions and/or you haven't disabled UEFI in your PC's BIOS?.

http://gparted.org/livecd.php

Does your PC have a recovery partition and is that still intact?, make and model please!.

 

[yvessr]

my PC is a Acer Travelmate 6592G and it has NO UEFI...
I intend to reformat the C-partition (194 Go) on installation of the new Windows 10 Pro x64 Fr...

 

[yvessr]

 

[Wolfie]

I intend to reformat the C-partition (194 Go) on installation of the new Windows 10 Pro x64 Fr...

Is that the same version you started with or are you trying to upgrade from Home to Pro?.

 

[yvessr]

hello @Wolfie...
... after several 'blue screens' and finally 'full black screen' and even deny to startup I decided about 3 weeks ago to reinstall a new version of Win10 (besides the buggy old one). It succeeded and it appears that now I am running a Windows 10.0 Home Unilingual version 10240 !!!, but.... 'blue error screens' continue to appear (Twice or 3 times a day) and this is, at least, very unpleasant !
Therefore I decided to reinstall a clean Windows from a bootable USB stick on the C partition with reformatting...
Unfortunately it seem impossible to boot up my PC from that (bootable made with Rufus) USB-stick...???

 

[Wolfie]

You can also try UNetbootin for Windows instead of Rufus:

https://unetbootin.github.io/

 

[yvessr]

OK @Wolfie , I wil try that immediately; just want to mention that a bootable USB has also been made from within MediaCreationTool , but that brought me the same issue !!!...

 

[Wolfie]

Did you fully pre-format the USB stick to FAT32 before you used the Media Creation Tool?, you might want to do that first to get rid of any unwanted files on the stick!.

 

[yvessr]

Yes I did @Wolfie, now I just downloaded the most recent RTM (10240) esd, and I will give it a try...

oeps... When writing to you I just got another 'blue screen' , driver_irql_not_less_or_equal (netwlv64.sys), and I really am desperate !!!... and absolutely get rid of such issues !

 

[Trouble]

I just got another 'blue screen' , driver_irql_not_less_or_equal (netwlv64.sys)

Your crash errors may have more to do with your Intel wireless adapter's lack of comaptibiity with Windows 10 than anything else.
IF you Google that error you will find many instances of people with similar issues with that adapter.
http://www.tomshardware.com/answers/id-2806293/driver-ipql-equal-netwlv64-sys.html

 

[yvessr]

Hi @Trouble,
You might be right... I found and just ordered another Intel wifi card... so wait and see...
Thanks for the link !

 

[Trouble]

Thanks for the link !

You bet.
Good luck and please keep us posted as to your progress.

 

[yvessr]

Fine, that might be the solution for one of my problems, but I still cannot repair my system files !!!...
As I wrote SFC tells me there are problems but they cannot be repaired and Dism won't work; files are not found !
I tried it with several paths (towards as well .wim as .esd installers), but always ... not found
What can I do to repair those windows system files...? (Win10 reinstall nor repair are accepted !)
Any suggestion ???

 

[yvessr]

Hi all,
I am still NOwhere with my quest for repairing timpohe windows system files and upgrade to Win10 1703 is impossible !...
I tried to examine the CBS.LOG created after aanother SFC /scannow trial and it seemes to me that there are 5 dll files wich give a 'cannot repair...' report:
these are: KBDNO.DLL, KBDSL.DLL, KBDNEPR.DLL, KBDNSO.DLL and KBDNKO.DLL. (keyboard language files).
they all gave me a similar return like this one:

2017-07-28 19:53:49, Info CSI 00001d32 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..l-keyboard-00090c00_31bf3856ad364e35_10.0.10240.16384_none_ab1080b2861dada1\kbdnko.dll do not match actual file [l:20{10}]"kbdnko.dll" :
Found: {l:32 b:BnvnUr9fNl/JtwhJbcf49WkVoPHqTszRFCI7s6g0nAs=} Expected: {l:32 b:+sNr7zmzm4Zj90/fW6QC/ETPuUeX4PzpZi97VAymMfo=}
2017-07-28 19:53:49, Info CSI 00001d33 [SR] Cannot repair member file [l:20{10}]"kbdnko.dll" of Microsoft-Windows-International-Keyboard-00090c00, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-07-28 19:53:49, Info CSI 00001d34 [SR] This component was referenced by [l:346{173}]"Microsoft-Windows-Client-Features-Package-AutoMerged-windows~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-windows-Deployment"
2017-07-28 19:53:49, Info CSI 00001d35 Hashes for file member \??\C:\Windows\System32\kbdnko.dll do not match actual file [l:20{10}]"kbdnko.dll" :
Found: {l:32 b:BnvnUr9fNl/JtwhJbcf49WkVoPHqTszRFCI7s6g0nAs=} Expected: {l:32 b:+sNr7zmzm4Zj90/fW6QC/ETPuUeX4PzpZi97VAymMfo=}
2017-07-28 19:53:49, Info CSI 00001d36 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..l-keyboard-00090c00_31bf3856ad364e35_10.0.10240.16384_none_ab1080b2861dada1\kbdnko.dll do not match actual file [l:20{10}]"kbdnko.dll" :
Found: {l:32 b:BnvnUr9fNl/JtwhJbcf49WkVoPHqTszRFCI7s6g0nAs=} Expected: {l:32 b:+sNr7zmzm4Zj90/fW6QC/ETPuUeX4PzpZi97VAymMfo=}
2017-07-28 19:53:49, Info CSI 00001d37 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"kbdnko.dll"; source file in store is also corrupted

I tried to replace them by freshly downloaded files but that seems impossible (Trustedinstaller ownership)... also declaring myself as administrator and owner of the system32 directory didn't unlock those files...

Can some of you PLEASE help me to get around my problems ?

THANX a lot !

 

[yvessr]

Hi all,

.... I am very sad... still NO reply nor PM !
PLEASE can someone help me to restore my system files because it's impossible to upgrade my actual Win10 10240 to Creators !

 

[Trouble]

I tried it with several paths (towards as well .wim as .esd installers), but always ... not found

Download the ISO for Windows 10 from here
https://www.microsoft.com/en-us/software-download/windows10
It must match your currently installed version of Windows 10

Once you have the ISO downloaded to your computer, double click it to mount it.
That will produce a virtual drive on your computer with a drive letter. Make note of the Drive Letter.
Inspect the mounted drive in the directory of
Drive Letter\Sources
For the file name "install.wim" OR "install.esd"
Depending on what you find and the Drive Letter use one of the following

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess (where X:\Sources\Install.wim is the location of the file)

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.esd:1 /LimitAccess (where X:\Sources\Install.esd is the location of the file)

Yours will not likely be X:\ but will more likely be another Drive Letter

 

[yvessr]

Hi @Trouble,
Thank you for your suggestion !
I did exactly what you described on a 'V'-drive but , unfortunately, Dism returned me the same error 0x800f081f message !
what's going wrong ???????????????????????