Mounting image error 0xc1420127

Одныжды, мне понадобилось смонтировать (dism /Mount-WIM) установочный образ Windows 7 и провести ряд манипуляций. К сожалению компьютер был ...

Одныжды, мне понадобилось смонтировать (dism /Mount-WIM) установочный образ Windows 7 и провести ряд манипуляций. К сожалению компьютер был перезагружен до процесса демонтирования образа (dism /Unmount-WIM).

В результате получилось так, что образ с индексом 3 был помечен как смонтированный, и при попытке смонтировать его появлялась ошибка:

Cистема DISM
Версия: 6.1.7600.16385

Ошибка: 0xc1420127

Указанный образ в указанном WIM-файле уже подключен с доступом на
чтение и запись.

Файл журнала DISM находится по адресу C:WindowsLogsDISMdism.log

Команда dism /Unmount-wim /MountDir:»C:DeploymentWINDOWS 7mount» /Discard тоже завершалась ошибкой

dism /Unmount-wim /MountDir:"C:DeploymentWINDOWS 7mount" /Discard

Cистема DISM
Версия: 6.1.7600.16385

Ошибка: 50

The request is not supported.

Файл журнала DISM находится по адресу C:WindowsLogsDISMdism.log

Попробовал демонтировать образ с помощью Imagex

imagex /UNMOUNT "C:DeploymentWINDOWS 7mount"

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Unmount Error: Did not find an image mounted to [C:DeploymentWINDOWS 7mount].

«Хммм…» — подумал я и решил смонтировать образ с помощью Imagex, чтобы потом красиво размонтировать. Imagex ругнулся, но с задачей справился.

imagex /MOUNT "C:DeploymentWINDOWS 7install.wim" 3 "C:DeploymentWINDOWS 7mount"

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Mounting: [C:DeploymentWINDOWS 7install.wim, 3] -> [C:DeploymentWINDOWS 7mount]...

[   0% ] Mounting progress
[ WARN ] An objectID is in use on this volume for [C:DeploymentWINDOWS 7mountUsersAdministratorDesktop].
Committing or capturing this image will lose objectID information. Please mount or apply to another volume.

[ WARN ] An objectID is in use on this volume for [C:DeploymentWINDOWS 7mountUsersAdministratorDocuments].
Committing or capturing this image will lose objectID information. Please mount or apply to another volume.
[ 100% ] Mounting progress

Successfully mounted image.

Total elapsed time: 14 min 44 sec

Далее делаю imagex /UNMOUNT

imagex /UNMOUNT "C:DeploymentWINDOWS 7mount"

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Unmounting: [C:DeploymentWINDOWS 7mount]...

[ 100% ] Mount cleanup progress

Successfully unmounted image.

Total elapsed time: 3 min 54 sec

С первого взгляда всё ОК, но при попытке смонтировать образ с помощью dism /Mount-wim всё та же ошибка 0xc1420127.

Внимание, Solution!

Немного подумав, проверяю какие опции нам доступны в команде dism и вижу /Cleanup-Wim

  /Cleanup-Wim   - Удаляет ресурсы, связанные с поврежденными подключенными образами WIM.

То, что надо! Пробую:

dism /Cleanup-WIM:"C:DeploymentWINDOWS 7install.wim"

Cистема DISM
Версия: 6.1.7600.16385

Отключение образа в C:DeploymentWINDOWS 7mount!
[==========================100.0%==========================]
Поиск устаревших файлов на диске C
Операция успешно завершена.

Теперь всё понастоящему ОК: крманда dism /Mount-wim /wimfile:»C:DeploymentWINDOWS 7install.wim» /index:3 /MountDir:»C:DeploymentWINDOWS 7mount» выполняется без ошибок.

  • Remove From My Forums
  • Question

  • I am trying to add a network driver to a 64 bit Windows 7 boot image.  I get the error:

    Error Occurred while trying to execute this command.

    Error Code: 0xc1420127

    The driver is for an HP 8540p.  I was able to add drivers to it before but it seems like anything 64 bit won’t take.  I’ve deleted and reinstalled the image to no avail.  I’ve tried adding drivers with dism and that hasn’t resolved either.

    Please help!

Answers

  • If you were trying to add a driver to a boot wim and it failed resulting in that error code the following may help.

    1. Clear all your temp directorys.

    2. Browse to «HKEY_LOCAL_MACHINESOFTWAREMicrosoftWIMMountMounted Images» and delete any keys below this.

    WDS should now allow you to add drivers to the boot.wim.

    • Proposed as answer by

      Wednesday, March 2, 2011 4:02 PM

    • Marked as answer by
      Anthony_Mann
      Thursday, May 3, 2012 3:12 AM

    • Proposed as answer by
      Miya Yao
      Thursday, August 12, 2010 9:59 AM
    • Marked as answer by
      Miya Yao
      Thursday, August 19, 2010 8:41 AM

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 0xc1420127 and 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.

  1. press Windows key and R key together
  2. type in regedit and press enter
  3. Go to the following registry location and delete sub keys of Mounted Images: "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWIMMountMounted Images"

Source

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 0xc1420127 and 0xc190010b Windows Update errors.

Therefore, here’s some more general Windows maintenance advice for you:

Clean-up your Windows system

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:

  1. press Windows key and R key together
  2. type in %temp% and press enter
  3. delete the all files and folders

Clear all downloaded Windows Update files:

  1. press Windows key and E key together
  2. go to C:WindowsSoftwareDistributionDownload
  3. delete all files and folders

Clean up Windows Temp folder:

  1. press Windows key and E key together
  2. go to C:WindowsTemp
  3. delete all files and folders

Disk Clean-up

  1. To open Disk Cleanup from the desktop, swipe in from the right edge of the screen, tap Settings (or if you’re using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Settings), tap or click Control Panel, type Admin in the Search box, tap or click Administrative Tools, and then double-tap or double-click Disk Cleanup.
  2. In the Drives list, choose the drive you want to clean, and then tap or click OK.
  3. In the Disk Cleanup dialog, select the checkboxes for the file types that you want to delete, tap or click OK, and then tap or click Delete files.
  4. There are more Windows locations to clean up and regain extra disk space in Windows.

(more options & information)

  • Uninstall unnecessary programs through Control Panel > Programs > Uninstall a program

Talking about Windows disk clean-up, I have a post summing up 5 extra ways to clean up disk space in Windows Server!

Deactivate anti-virus programs

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.

Install all available & pending Windows updates first

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.

Check for corrupted Windows files with SFC.exe

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.

  1. press Windows key and type cmd
  2. when CMD is displayed in the search results, click on it with the right mouse button and choose Run as administrator
  3. type sfc /? to review its help and options, and sfc /scannow to scan your system

(more options & information)

Delete $Windows~BT directory

When a Windows 10 update has failed, you’ll find (some of) its files in a directory C:$Windows~BT. The $WINDOWS.~BT and $WINDOWS.~WS folders are associated with the Windows 10 upgrade process. Automatically downloaded Windows 10 installation files are in the $WINDOWS.~BT folder. On Windows 10, the $WINDOWS.~BT folder contains your previous Windows installation.

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

Code language: PowerShell (powershell)

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

Code language: PowerShell (powershell)

Fix Microsoft Windows Update Issues

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 8.1 to Windows 10 update should work just fine.

How to look up Windows error codes with Err.exe

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).

For example 0xc190010b

C:tempErr>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"

Code language: PowerShell (powershell)

0xc1420127

C:tempErr>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"

Code language: PowerShell (powershell)

Понравилась статья? Поделить с друзьями:
  • Morrowind как изменить внешность
  • Modinfo error module drbd not found
  • Modern error victim of a modern age 2023
  • Mmloaddrv exe ошибка как исправить
  • Minecraft opengl error 1285 out of memory