[German]Users who want to upgrade to Windows 10 version 1903 may get an error message with the code 0xc190012e. Here is a rough overview, whereby I cannot name any cause for the error at the moment. There is only a suspicion, it could be SSD related.
However, I’ll publish this error within the blog – maybe a reader as another explanation of the cause of the error.
A hint for readers to error 0xC190012E
German blog reader Dirk S. had contacted me a few days ago by mail and pointed out the problem. Dirk wrote.
There is a relatively new but persistent bug with the current update/upgrade.
I’ve tried this with all the variants recommended so far and have an installation that stubbornly refuses to install.
Thinkpad X1 Yoga V2, W10 1809 up2date, no unusual bugs. I also switched off SDCard and USB in BIOS, no success.
Updatelog is also not very informative for me.
On your pages, which by the way are among the best and most informative for me, I haven’t found anything yet.
Are there already analyses and/or other reports?
I haven’t recognized this error and did not cover it within my blog. For me, it seems, that this error codes has been introduced with Windows 10, version 1903 at all. That’s what I replied to the user, who answered:
seems to be a single destiny. If you get more messages, here is a candidate for trials and logfiles.
Microsoft reports to the bug that this would probably be fixed sometime and you may wait. But I have little confidence in such announcements.
Only a few mentions on the Internet
Of course I immediately started an internet search, if there is a hint there. For insider previews of build 18290.1000 there were already cases where the bug was reported at the end of December 2018. You can find this thread on reddit.com.
Error code 0xc190012e when attempting to install version 1903 of Windows.
When I attempt to install the update to version 1903 of windows,I get error code 0xc190012e. I’ve tried to fix it by wiping the software distribution folder and temporarily stopping the update service,but none of it seems to work. What else can I try?
There came the hint to uninstall the program BattlEye (an AntiCheat technology for games) and delete the associated files. Microsoft has documented that older versions of the BattlEye software are not compatible with Windows 10 V1903 in the Windows 10 V1903 status dashboard. However, the Windows setup should detect the software and prevent the upgrade immediately. Microsoft also writes that this Prolem is already fixed by BattlEye for all current games with an update. I wouldn’t consider the reddit.com hint to be so valid now. But there is als a hint within the thread, that one user has a system with a SSD Samsung 840 120G …
Volume too fragmented to install?
On Twitter I became aware of this tweet came, which could provide some clues – but I’m not sure, whether this is true.
First time I’ve seen that one! “The volume is too fragmented to complete this operation”. Are you running a standard drive or an SSD?
— Windows Insider (@windowsinsider) 7. November 2018
A user gives the above answer to an error request. The volume on which Windows 10 V1903 is to be installed is too fragmented. The question of whether an SSD is in use immediately arises there. The affected person has an SSD (Samsung 850 EVO) – and I found that in other threads as well.
SSDs to blame?
I then asked the reader who reported the error whether he also had a Samsung 850 EVO. His feedback was interesting.
no, that’s a SSD Samsung 960 per 2Tb but also quite full. Fragmentation doesn’t really play a role anymore with SSDs. But if borderline filled perhaps nevertheless. I delete something from it and then try it again, but will certainly only what next weekend.
That is at least a hint for further investigations. Maybe it will help someone to dig a bit deeper.
At this point, another clutter of Windows as a Service (WaaS) becomes obvisious. Since Microsoft’s developers constantly implement new error codes in feature updates, but Microsoft does not publish any documentation on the meaning of the error codes, users are left the dark. Maybe the definition files in Windows 10 V1903 SDK contain more information, but I won’t install them, hoping to find some info. The tools I use to analyze the error code show it as unknown. Anyone who knows a reason for this error code? Maybe somebody can confirm mit SSD suspicion.
Addendum from the German reader
GErman blog-reader Dirk hastested my suggestions again. He wrote me the following by mail:
well, I tried again the way over the image on USB that always buck so far also, that gave then the next error:
“This PC can’t be upgraded to Windows 10” error on a computer that has a USB device or SD card attached
Applies to: Windows 10, version 1903
New was the hint:
If you are using installation media (USB flash drive, DVD, or ISO file) to install Windows 10, copy the files on the installation media to your local drive, and then start the installation from the local drive.
So copy the image to the disk (SSD) and start it from there. There was then only incompatibility with VMWare Workstation Pro 15.0.2 and after the update to 15.1 also the upgrade to W 10 1903 went through.
Dirk also wrote to me: “I think that the internal checks for upgradeability are not quite mature and are now much too complex and therefore often fail. Nevertheless, it is better to exclude an installation that would be upgradeable (false negative) than to once again allow installations that are broken afterwards.
2nd addendum from a blog reader
In August 2019, there was another tip from blog reader Oliver, who provided the following information:
The upgrade from 1803 to 1903 just went trough, but:
- Only via the 1903 Media Creation Tool ISO (only with option ‘keep everything’, so created with the system install language)
- WU Menu threw the above code as well as the separate Upgrader
- 1803 -> 1809 I could not execute successfully for months because of alleged GPU slope (setupdiag referred to the nVidia driver), but 1803 -> 1903 works. Great sausage. Nothing is ported back to Fixes -_-
* System on ner 860 Evo and two Crucial SSDs as data stockpile (Windows only sees RAW because of VC). Antivirus and Firewall were paused and the system partition was decrypted, MS isn’t testing anymore……
My conclusion: The separate Upgrader is what they also distribute via WSUS, and that is either dirt per se or simply outdated. So the ISO-Builder either pulls another Upgrader or does a completely different procedure anyway.
I’d laugh if it’s the language pack that causes the issue and only the error code is wrong! Maybe it’s a CatchAll and the subprocedure that the WSUS may get from en-US just returns “error” on my de-DE and the parent makes it 0xc190012e.
Anyway: They really can’t cope anymore with what the left and right hand does as you can see in many cases :/
At this point, thanks to the blog readers for their feedback.
Windows 10 Update error 0xC1900208
Windows 10: A Feature Upgrade drops error 0xC1900209
Windows 10: Upgrade error 0xC1900101 – 0x20003
Windows 10: Upgrade error 0xC1900101-0x2000C
Windows 10: Upgrade error 0xC1900101-0×20017/0x30017
Windows 10: Upgrade error 0xC1900101-0x2000A
Windows 10: Upgrade error 0xC1900101 – 0x20004
Cookies helps to fund this blog: Cookie settings