{"id":10138,"date":"2019-06-19T00:17:00","date_gmt":"2019-06-18T22:17:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10138"},"modified":"2024-10-05T18:27:06","modified_gmt":"2024-10-05T16:27:06","slug":"windows-10-upgrade-to-v1903-end-with-error-0xc190012e","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/06\/19\/windows-10-upgrade-to-v1903-end-with-error-0xc190012e\/","title":{"rendered":"Windows 10: Upgrade to v1903 end with error 0xc190012e"},"content":{"rendered":"

[German<\/a>]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.<\/p>\n

<\/p>\n

\"\"However, I'll publish this error within the blog – maybe a reader as another explanation of the cause of the error.<\/p>\n

A hint for readers to error 0xC190012E<\/h2>\n

German blog reader Dirk S. had contacted me a few days ago by mail and pointed out the problem. Dirk wrote.<\/p>\n

There is a relatively new but persistent bug with the current update\/upgrade.<\/p>\n

I've tried this with all the variants recommended so far and have an installation that stubbornly refuses to install.<\/p>\n

Thinkpad X1 Yoga V2, W10 1809 up2date, no unusual bugs. I also switched off SDCard and USB in BIOS, no success.<\/p>\n

Updatelog is also not very informative for me.<\/p>\n

On your pages, which by the way are among the best and most informative for me, I haven't found anything yet.<\/p>\n

Are there already analyses and\/or other reports?<\/p><\/blockquote>\n

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:<\/p>\n

seems to be a single destiny. If you get more messages, here is a candidate for trials and logfiles.<\/p>\n

Microsoft reports to the bug that this would probably be fixed sometime and you may wait. But I have little confidence in such announcements.<\/p><\/blockquote>\n

Only a few mentions on the Internet<\/h2>\n

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<\/a> at the end of December 2018. You can find this thread on reddit.com<\/a>.<\/p>\n

Error code 0xc190012e when attempting to install version 1903 of Windows.<\/p>\n

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?<\/p><\/blockquote>\n

There came the hint to uninstall the program BattlEye<\/a> (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<\/a>. 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 …<\/p>\n

Volume too fragmented to install?<\/h3>\n

On Twitter I became aware of this tweet came<\/a>, which could provide some clues \u2013 but I'm not sure, whether this is true.<\/p>\n

\n

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?<\/p>\n

\u2014 Windows Insider (@windowsinsider) 7. November 2018<\/a><\/p><\/blockquote>\n