Last weekend I had to update my girlfriends laptop from Windows 8.1 to Windows 10. Some might say, an easy task. Well, it wasn’t. After downloading the Windows 10 update through Windows Update, Windows Update returned errors
0xc190010b, even using the Windows 10 media creation tool. And as always there are many reasons for these errors. In this short post, I’ll provide some possible solutions and tips.
tl;dr, in my specific case, a WIMMount mounted image was the wrongdoer, and I had to delete that faulty mount point:
Delete sub keys of Mounted Images and check.
regeditand press enter
After deleting the sub key of Mounted Images in the Windows registry, the Windows 10 setup worked perfectly for me. There may be other issues involved as well when you’re facing these
0xc190010b Windows Update errors.
Therefore, here’s some more general Windows maintenance advice for you:
Lack of disk space may cause various Windows Update errors. Always keep your disk clean, regularly clean up your temporary directories and unneeded download files.
Clear all your temp directories:
%temp%and press enter
Clear all downloaded Windows Update files:
Clean up Windows Temp folder:
Talking about Windows disk clean-up, I have a post summing up 5 extra ways to clean up disk space in Windows Server!
An activated anti-virus program may interfere with the Windows 10 update, so temporarily disable your AV software. Usually there is an icon at the lower-right corner of your screen, use the left or right mouse button to pull up its menu and choose disable.
It’s possible you haven’t installed all available Windows updates yet, and one of them is needed for the Windows 10 update to install successfully. Always install all available and pending updates, it keeps your computer more secure – as vulnerabilities are fixed – often makes your computer run faster as an update is more optimized.
The System File Check utility, or
sfc.exe is used to verify the integrity of important Windows files. When used properly,
sfc.exe repairs corrupted system files.
sfc /?to review its help and options, and
sfc /scannowto scan your system
When a Windows 10 update has failed, you’ll find (some of) its files in a directory
C:\$Windows~BT. Before trying the update again, the directory needs to be deleted – or if all else fails, renamed. Open up a CMD command line prompt as administrator, and execute:
cd \ rd /s /q \$Windows~BT
If you’re an advanced Windows power user, you could try changing file- and directory permissions and ownership if the command should fail. Otherwise, just rename the directory:
ren \$Windows~BT \$Windows~BT.old
And last but not least: Learn how to keep Windows up to date, fix errors and other issues with Windows Update. Fix the problem yourself or get help from the community:
Microsoft Support website.
And that’s it. After all this, your Windows 10 update from Windows 8.1 should work just fine.
What’s the meaning of 0xc1420127 and 0xc190010b? Just look it up with
err.exe, Err.exe is a great command-line utility for looking up error codes. Get Err.exe at http://www.microsoft.com/downloads/details.aspx?familyid=be596899-7bb8-4208-b7fc-09e02a13696c&displaylang=en (MSDN says it’s for Exchange error codes but it works for Win32 error codes and many more).
C:\temp\Err>Err.EXE c190010b # as an HRESULT: Severity: FAILURE (1), Facility: 0x190, Code 0x10b # for hex 0x10b / decimal 267 : MMIOERR_PATHNOTFOUND mmsystem.h MCIERR_MISSING_COMMAND_STRING mmsystem.h STATUS_NOTIFY_CLEANUP ntstatus.h # This indicates that a notify change request has been # completed due to closing the handle which made the notify # change request. SQL_267_severity_16 sql_err # Object '%.*ls' cannot be found. ERROR_DIRECTORY winerror.h # The directory name is invalid. # 5 matches found for "c190010b"
C:\temp\Err>Err.EXE c1420127 # as an HRESULT: Severity: FAILURE (1), Facility: 0x142, Code 0x127 # for hex 0x127 / decimal 295 : MCIERR_DUPLICATE_FLAGS mmsystem.h STATUS_INTERRUPT_VECTOR_ALREADY_CONNECTED ntstatus.h # The specified interrupt vector was already connected. SQL_295_severity_16 sql_err # Syntax error converting character string to smalldatetime # data type. # 3 matches found for "c1420127"
Featured image via Flickr by Alex Roberts
My name is Jan. I am not a hacker, coder, developer, programmer or guru. I am merely a system administrator, doing my daily thing at Vevida in the Netherlands. With over 15 years of experience, my specialties include Windows Server, IIS, Linux (CentOS, Debian), security, PHP, WordPress, websites & optimization. Want to support me and donate? Use this link: https://paypal.me/jreilink.
Install Windows Server Servicing Stack Updates (SSU) using PowerShell
Security baseline for Windows 10 v1903 and Windows Server v1903 – final release
Setting up Monit monitoring in Windows Subsystem for Linux WSL
How to verify SMBv1 is disabled in Windows and Windows Server