Windows 10: How to fix the «the MultiEdition key from the blackboard» error occurred while installing…
Discus and support How to fix the «the MultiEdition key from the blackboard» error occurred while installing… in Windows 10 Installation and Upgrade to solve the problem; I want to install Windows 10 on my computer but the installer suddenly stops while installing it without any error messages and there was the following…
Discussion in ‘Windows 10 Installation and Upgrade’ started by Amir Mohsen Ghasemi, Mar 30, 2021.
-
How to fix the «the MultiEdition key from the blackboard» error occurred while installing…
I want to install Windows 10 on my computer but the installer suddenly stops while installing it without any error messages and there was the following error in the setuperr.txt file inside the $WINDOWS.~BT/Sources/Panther folder.
[COLOR=rgba215, 57, 0, 1]2021-03-10 15:34:09, Error [0x060126] IBS Callback_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490][/COLOR]
So, how can I fix the error above? It’s worth mentioning that I use an USB to install Windows and made it bootable using Rufus software.
-
Blackboard
Hi,
Thank you for posting your query on Microsoft Community.
As per the description, I understand that you are facing some issues using Windows 10.
I would suggest you to refer to the suggestions by Pinaki Mohanty replied on March 27, 2014 and check if that helps.
Blackboard website error «Internet Explorer has Stopped Working» on Internet Explorer 11
Hope this information helps. Please let us know if you need any other assistance with Windows in future. We will be happy to assist you.
-
Blackboard
The browser checker for Blackboard consistently states I’m not using IE Explorer 11 and JRE is Incorrectly Installed or Not Installed or Not supported. I checked if I had the latest IE browser and I went to Java.com, like Blackboard recommended, to download
the latest version. Can anyone assist in this matter? -
How to fix the «the MultiEdition key from the blackboard» error occurred while installing…
Blackboard collaborate will not connect with windows 10/ edge
Hi Flora,
Thank you for writing your query in Microsoft Community.
You might be facing this issue due to a corrupted app or some changes in application settings. I suggest you to try the following steps and check if it helps.
Let’s first run the Apps Troubleshooter and check if that helps. The Apps Troubleshooter is an automated tool which we have developed to address a number of known issues that can prevent the Apps from running properly. This troubleshooter
automatically fixes some issues, including suboptimal screen resolution, incorrect security or account settings etc. You can click on this link to download and run the Apps troubleshooter.Run the troubleshooter:
Fix problems with apps from Microsoft Store
If still this issue persists, you can also contact the blackboard collaborate for further support.
https://www.blackboard.com/Platforms/Collaborate/Support/Support-for-Blackboard-Collaborate.aspx
Hope this helps. Reply us back with the results we will be happy to assist you.
How to fix the «the MultiEdition key from the blackboard» error occurred while installing…
-
How to fix the «the MultiEdition key from the blackboard» error occurred while installing… — Similar Threads — fix MultiEdition key
-
How to fix error occurred while attempting to delete this specific element
in Windows 10 Software and Apps
How to fix error occurred while attempting to delete this specific element: So i unchecked the number of processors in msconfig i couldn’t get into windows i tried everything like chkdsk,sfc system restore and nothing worked so today i saw this post with a fix to change the msconfig settings from the cmd in windows advanced options here are the… -
How to fix error occurred while attempting to delete this specific element
in Windows 10 BSOD Crashes and Debugging
How to fix error occurred while attempting to delete this specific element: So i unchecked the number of processors in msconfig i couldn’t get into windows i tried everything like chkdsk,sfc system restore and nothing worked so today i saw this post with a fix to change the msconfig settings from the cmd in windows advanced options here are the… -
How to fix error occurred while attempting to delete this specific element
in Windows 10 Gaming
How to fix error occurred while attempting to delete this specific element: So i unchecked the number of processors in msconfig i couldn’t get into windows i tried everything like chkdsk,sfc system restore and nothing worked so today i saw this post with a fix to change the msconfig settings from the cmd in windows advanced options here are the… -
Error is occuring while installing window 11
in Windows 10 Software and Apps
Error is occuring while installing window 11: Hello, I am Huzaifa from Newyork. I am facing some problems in whichThe same error is occurring to me while installing Windows 11.I have access to several TB of storage. I possess several internal HD. «Chkdsk cannot run because the volume is in use by another process,» says… -
How to fix «an error has occurred while troubleshooting, validiting the integrity of the…
in Windows 10 Gaming
How to fix «an error has occurred while troubleshooting, validiting the integrity of the…: HellooThere occurs a problem: all troubleshooters can’t work correctly can not run in my laptop. No matter what Diagnostic I run, there’l always be this error. My type windows is Windows 11 Home insider preview single language-Version DEV OS Build 22449.1000.it’s always show… -
How to fix «an error has occurred while troubleshooting, validiting the integrity of the…
in Windows 10 Software and Apps
How to fix «an error has occurred while troubleshooting, validiting the integrity of the…: HellooThere occurs a problem: all troubleshooters can’t work correctly can not run in my laptop. No matter what Diagnostic I run, there’l always be this error. My type windows is Windows 11 Home insider preview single language-Version DEV OS Build 22449.1000.it’s always show… -
How to fix An error occurred while starting Roblox
in Windows 10 News
How to fix An error occurred while starting Roblox: [IMG]Roblox is an online game platform where users can design their games or play games by other users, but sometimes users will receive an error stating that “An error occurred while starting Roblox Studio” and as no clue what to do. This tutorial will explain what causes… -
While windows installing, a unexpected error occur
in Windows 10 Installation and Upgrade
While windows installing, a unexpected error occur: I reinstalled the windows. When I try to install it, it say there are some unexpected error occur and my install is fail. I try reinstall like 10 times but it fails. What can I do?[IMG]… -
Error occurs while installing updates
in Windows 10 Installation and Upgrade
Error occurs while installing updates: • Feature update to Windows 10, version 1803 — Error 0x8007007e• Update for Windows 10 Version 1607 for x64-based Systems (KB4033631) — Error 0x8000ffff
• Update for Windows 10 Version 1607 for x64-based Systems (KB4049411) — Error 0x8000ffff
• Update for Windows 10…
Users found this page by searching for:
-
An error occurred while removing the MultiEdition key from the blackboard
,
-
an error occured while removing the multiedition key from the blackboard
-
I’ve discovered this issue a few months ago, and have found literally no solutions to fixing this issue. Basically, whenever I use a Windows 10 1709 WIM file, any edition I select gives me this error message:
This does not happen with any other version of Windows 10, even versions as old as RTM 1507. This also doesn’t happen if I use an older version of the Windows Setup (1709 or lower), which happily accepts any 1709 image I provide it. Attempting to use autounattend.xml to skip the licence agreement page doesn’t work either (same error in the screenshot above comes up and halts the setup).
I’m also not sure if this is related to a similar issue a friend of mine was having (Windows Embedded 7 WIM files showing the same exact error in newer versions of Windows Setup).
Could someone please tell me why this issue happens and how I can fix the issue?
-
Iirc, this happens when the setup.exe from the boot.wim index 2 sources folder doesn’t match the setup.exe from the isosources folder.
Running a test
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
I checked both of those files, and both have the same SHA1 hash and filesize.
-
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
Do you use the SWM format (split WIM)? In this case, the license documents must reside inside the first part of the SWM.
-
I did the test with a 2200MB split wim (install.swm + install2.swm) file set, no error.
Next i created 23 install.swm files, 100MB each, and no error too.When i open the first install.swm file of the 100MB split wims, it contains the license files (license.rtf).
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
-
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
-
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
I followed the steps exactly as you stated in the post and created an ISO, which I then proceeded to use in VMWare.
This is what appeared upon booting from the ISO, went straight to starting the setup.
Asked for the language settings, and I clicked next.
It asked which edition I wanted, so I left it at the default selection and clicked next.
Then it stopped at the same error I was encountering about missing Software License Terms.
I checked the hashes again, and they were the same as the one you posted. I’m not sure what is going on at this point.
-
You get this message when the channel and index cannot find the appropriate license rtf file.
If it normally installs a volume GVLK that activates with KMS, sometimes they won’t include a retail license.
You can solve this in one of two ways.
First you can make a license for the retail channel, which I wouldn’t recommend.
Second you can alter or create the ei.cfg file in the iso’s sources folder
The contents of the ei.cfg file should be as follows: -
I already created an ei.cfg file with those same contents. The error coming up appears with or without the ei.cfg file. I also did some more testing and found the same exact issue happens with any Windows Embedded 7 WIM images as well, even ones I captured from an offline system with the DISM command.
Speaking of the license.rtf files, where exactly are they all located? I know that Windows 7 ISOs had them in the sources directory, but that seems to have changed with Windows 8 and up.
-
They’re in the install index in a subfolder in the Windows directory if I remember correctly. If you mount your index and search for rtf files in the Windows folder you should be able to find them.
-
Yeah, I found them. Still doesn’t make sense how the setup can’t find them when they’re in what I assume is the proper place («WindowsSystem32en-US» for English). I guess this is also why certain versions of Windows will always show an error with the Windows 10 Setup, like WES7.
Is there another place that the setup checks for the licence.rtf files? Or was is hard-coded to look through the install.wim?
-
I encountered this error a long time ago.
this happens when using the installation media of 1803 (or newer), together with a WIM file, which includes the enterprise SKU of 1709 or older (including enterprise SKUs of windows 8.1 and 7).
if I remember correctly, it has to do with how 1803 (or newer) setup files look up the license for the enterprise SKU.
older setups (before 1803) are looking for an enterprise license, while beginning with 1803, the setups look for a professional license when you try to install an enterprise SKU.-andy-
-
I have seen this error on VM’s if there is too little RAM allocated.
How much RAM does the machine have? -
It may help to read the setup logs
they should be in X:WindowsPanther
copy it to another location (or the C: drive if it’s formatted) -
I totally forgot to press next.
Got the same error (the previous test worked), here are the logs:
setuperr.log
2019-09-03 10:53:20, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490] 2019-09-03 10:53:23, Error IBS Callback_License_LoadLicenseText: SkuGetImageEulaAsString Failed to get the EULA; hr = 0x80070490:[gle=0x00000003] 2019-09-03 10:53:23, Error [0x060613] IBS Callback_License_LoadLicenseText:An error occurred while retrieving the EULA; hr = 0x80070490[gle=0x00000490]
diagerr.xml
<z:row Cls="D" Sev="33554432" Maj="Def" Min="Def" LN="1071" Fil="" Fun="CallBack_ImageWasSelectedInUi" Uid="33947942" Msg="CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard." PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="WinSetup.dll" Err="1168" MD="" DT="2019-09-03T10:53:20"/> <z:row Cls="D" Sev="33554432" Maj="Def" Min="Def" LN="474" Fil="" Fun="Callback_License_LoadLicenseText" Uid="33947648" Msg="Callback_License_LoadLicenseText: SkuGetImageEulaAsString Failed to get the EULA; hr = 0x80070490:" PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="WinSetup.dll" Err="3" MD="" DT="2019-09-03T10:53:23"/> <z:row Cls="D" Sev="33554432" Maj="Def" Min="Def" LN="510" Fil="" Fun="Callback_License_LoadLicenseText" Uid="33949203" Msg="Callback_License_LoadLicenseText:An error occurred while retrieving the EULA; hr = 0x80070490" PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="WinSetup.dll" Err="1168" MD="" DT="2019-09-03T10:53:23"/>
diagwrn.xml
<z:row Cls="D" Sev="50331648" Maj="Def" Min="Def" LN="2353" Fil="" Fun="LogCallback" Uid="50726604" Msg="GetDiskSMARTStatus: Disk does not support SMART failure detection." PID="968" TID="328" Con="" Exe="X:Sourcessetup.exe" Mod="WinSetup.dll" Err="1" MD="" DT="2019-09-03T10:53:11"/> <z:row Cls="D" Sev="50331648" Maj="Def" Min="Def" LN="470" Fil="" Fun="UnattendLogWV" Uid="50331648" Msg="[setup.exe] UnattendSearchSetupSourceDrive: Unable to convert ARC path [MULTI(0)DISK(0)CDROM(0)] to NT path; status = 0x80070002." PID="968" TID="1012" Con="" Exe="X:Sourcessetup.exe" Mod="UNATTEND.DLL" Err="0" MD="" DT="2019-09-03T10:53:11"/> <z:row Cls="D" Sev="50331648" Maj="diagnostic" Min="Def" LN="94" Fil="" Fun="CAccessWMI::LogErrorMessage" Uid="50790541" Msg="Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106" PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="diagnostic.dll" Err="1168" MD="" DT="2019-09-03T10:53:12"/> <z:row Cls="D" Sev="50331648" Maj="diagnostic" Min="Def" LN="94" Fil="" Fun="CAccessWMI::LogErrorMessage" Uid="50790438" Msg="Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0" PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="diagnostic.dll" Err="0" MD="" DT="2019-09-03T10:53:13"/> <z:row Cls="D" Sev="50331648" Maj="diagnostic" Min="Def" LN="94" Fil="" Fun="CAccessWMI::LogErrorMessage" Uid="50790438" Msg="Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0" PID="968" TID="1284" Con="" Exe="X:Sourcessetup.exe" Mod="diagnostic.dll" Err="0" MD="" DT="2019-09-03T10:53:21"/>
Attached Files:
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
Hello guys.
I followed this guide to do an installation to iSCSI target. Everything works fine until the last step. The installer report an error and rollback all changes.
the installer log are here:
setuperr.log
Code:
2020-05-17 19:14:20, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490]
2020-05-17 19:18:37, Error [0x06064c] IBS DeployIscsiDriversOffline: DISM.exe returned failure code 15105. DISM logs are at [F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log].
2020-05-17 19:18:37, Error [0x06064c] IBS DeployIscsiDriversOffline: Ensure the host OS and target OS are supported by Setup's iSCSI target boot support matrix.
2020-05-17 19:18:37, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x0]
iscsi_boot_net.log
Code:
2020-05-17 19:18:30, Info DISM PID=1732 TID=1688 Scratch directory set to 'X:windowsTEMP'. - CDISMManager::put_ScratchDir
2020-05-17 19:18:30, Info DISM PID=1732 TID=1688 DismCore.dll version: 10.0.18362.1 - CDISMManager::FinalConstruct
2020-05-17 19:18:30, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:30, Info DISM PID=1732 TID=1688 Successfully loaded the ImageSession at "\towerisoswin10_business_imageSources" - CDISMManager::LoadLocalImageSession
2020-05-17 19:18:30, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:30, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:30, Info DISM DISM Manager: PID=1732 TID=1688 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2020-05-17 19:18:30, Info DISM DISM.EXE:
2020-05-17 19:18:30, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2020-05-17 19:18:30, Info DISM DISM.EXE:
2020-05-17 19:18:30, Info DISM DISM.EXE: Host machine information: OS Version=10.0.19041, Running architecture=amd64, Number of processors=4
2020-05-17 19:18:30, Info DISM DISM.EXE: Dism.exe version: 10.0.18362.1
2020-05-17 19:18:30, Info DISM DISM.EXE: Executing command line: \towerisoswin10_business_imageSourcesdism.exe /logpath:F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log /Image:F: /Add-NetAdapter /HostAdapter:{15AB9265-7661-4D48-9A4E-0BF70794B5E3} /BootDriver:ms_tcpip /BootDriver:ms_tcpip6
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Connecting to the provider located at \towerisoswin10_business_imageSourcesFolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:30, Warning DISM DISM Provider Store: PID=1732 TID=1688 Failed to load the provider: \towerisoswin10_business_imageSourcesSiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-05-17 19:18:30, Warning DISM DISM Provider Store: PID=1732 TID=1688 Failed to load the provider: \towerisoswin10_business_imageSourcesFfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Connecting to the provider located at \towerisoswin10_business_imageSourcesWimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Connecting to the provider located at \towerisoswin10_business_imageSourcesVHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Connecting to the provider located at \towerisoswin10_business_imageSourcesImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:30, Warning DISM DISM Provider Store: PID=1732 TID=1688 Failed to load the provider: \towerisoswin10_business_imageSourcesMetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-05-17 19:18:30, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2020-05-17 19:18:30, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2020-05-17 19:18:30, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2020-05-17 19:18:30, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2020-05-17 19:18:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2020-05-17 19:18:30, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2020-05-17 19:18:30, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2020-05-17 19:18:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2020-05-17 19:18:30, Info DISM DISM Provider Store: PID=1732 TID=1688 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[1732] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified.
[1732] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[1732] [0xc142011c] WIMGetMountedImageHandle:(2906)
2020-05-17 19:18:30, Info DISM DISM WIM Provider: PID=1732 TID=1688 [F:] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2020-05-17 19:18:30, Info DISM DISM VHD Provider: PID=1732 TID=1688 [F:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2020-05-17 19:18:30, Warning DISM DISM Provider Store: PID=1732 TID=1688 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
2020-05-17 19:18:30, Info DISM DISM VHD Provider: PID=1732 TID=1688 [F:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2020-05-17 19:18:30, Info DISM DISM Imaging Provider: PID=1732 TID=1688 The provider VHDManager does not support CreateDismImage on F: - CGenericImagingManager::CreateDismImage
[1732] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified.
[1732] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[1732] [0xc142011c] WIMGetMountedImageHandle:(2906)
2020-05-17 19:18:30, Info DISM DISM WIM Provider: PID=1732 TID=1688 [F:] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2020-05-17 19:18:30, Info DISM DISM Imaging Provider: PID=1732 TID=1688 The provider WimManager does not support CreateDismImage on F: - CGenericImagingManager::CreateDismImage
2020-05-17 19:18:30, Info DISM DISM Imaging Provider: PID=1732 TID=1688 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2020-05-17 19:18:30, Info DISM DISM Manager: PID=1732 TID=1688 physical location path: F: - CDISMManager::CreateImageSession
2020-05-17 19:18:30, Info DISM DISM Manager: PID=1732 TID=1688 Event name for current DISM session is Global__?_Volume{3d08df48-bb2a-4d3e-8833-242ae67a9a72}__1449912551_131072_45278 - CDISMManager::CheckSessionAndLock
2020-05-17 19:18:30, Info DISM DISM Manager: PID=1732 TID=1688 Create session event 0x234 for current DISM session and event name is Global__?_Volume{3d08df48-bb2a-4d3e-8833-242ae67a9a72}__1449912551_131072_45278 - CDISMManager::CheckSessionAndLock
2020-05-17 19:18:30, Info DISM DISM Manager: PID=1732 TID=1688 Copying DISM from "F:WindowsSystem32Dism" - CDISMManager::CreateImageSessionFromLocation
2020-05-17 19:18:31, Info DISM DISM Manager: PID=1732 TID=1688 Successfully loaded the ImageSession at "X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330" - CDISMManager::LoadRemoteImageSession
2020-05-17 19:18:31, Info DISM DISM Image Session: PID=1624 TID=1816 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:31, Info DISM DISM OS Provider: PID=1624 TID=1816 Defaulting SystemPath to F: - CDISMOSServiceManager::Final_OnConnect
2020-05-17 19:18:31, Info DISM DISM OS Provider: PID=1624 TID=1816 Defaulting Windows folder to F:Windows - CDISMOSServiceManager::Final_OnConnect
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:31, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2020-05-17 19:18:31, Warning DISM DISM Provider Store: PID=1624 TID=1816 Failed to load the provider: X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:31, Info DISM DISM Provider Store: PID=1624 TID=1816 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2020-05-17 19:18:31, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:31, Info DISM Initialized Panther logging at F:$WINDOWS.~BTSourcesPantheriscsi_boot_net.log
2020-05-17 19:18:31, Info DISM DISM Manager: PID=1732 TID=1688 Image session successfully loaded from the temporary location: X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330 - CDISMManager::CreateImageSession
2020-05-17 19:18:31, Info DISM DISM OS Provider: PID=1624 TID=1816 Setting SystemPath to F: - CDISMOSServiceManager::SetSystemPath
2020-05-17 19:18:32, Info DISM DISM.EXE: Target image information: OS Version=10.0.18363.592, Image architecture=amd64
2020-05-17 19:18:32, Info DISM DISM.EXE: Image session version: 10.0.18362.1
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info CSI 00000001 Shim considered [l:125]'??F:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-05-17 19:18:32, Info CSI 00000002 Shim considered [l:122]'??F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_SUCCESS
2020-05-17 19:18:32, Info DISM DISM Package Manager: PID=1624 TID=1816 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2020-05-17 19:18:32, Info CSI 00000001 Shim considered [l:125]'??F:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-05-17 19:18:32, Info CSI 00000002 Shim considered [l:122]'??F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_SUCCESS
2020-05-17 19:18:32, Info CSI 00000001 Shim considered [l:125]'??F:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-05-17 19:18:32, Info CSI 00000002 Shim considered [l:122]'??F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_SUCCESS
2020-05-17 19:18:32, Info CBS Universal Time is: 2020-05-18 03:18:32.546
2020-05-17 19:18:32, Info CBS Failed to find a matching version for servicing stack: F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-05-17 19:18:32, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-05-17 19:18:32, Info CBS Offline servicing, using stack version from: F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9cbscore.dll
2020-05-17 19:18:32, Info CBS Loaded Servicing Stack v10.0.18362.590 with Core: F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9cbscore.dll
2020-05-17 19:18:32, Info CBS Setting core mode: CbsCoreModeOffline
2020-05-17 19:18:32, Info CSI 00000001@2020/5/18:03:18:32.687 WcpInitialize: wcp.dll version 10.0.18362.590 (WinBuild.160101.0800)
2020-05-17 19:18:32, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points.
2020-05-17 19:18:32, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
2020-05-17 19:18:32, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
2020-05-17 19:18:32, Info CBS Maint: idle processing paused
2020-05-17 19:18:32, Info DISM DISM Package Manager: PID=1624 TID=1816 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession
2020-05-17 19:18:32, Info CBS Lazy store initialization mode
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:32, Info CSI 00000001 Shim considered [l:125]'??F:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-05-17 19:18:32, Info CSI 00000002 Shim considered [l:122]'??F:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.590_none_5efc551459114cb9wcp.dll' : got STATUS_SUCCESS
2020-05-17 19:18:34, Info DISM DISM Driver Manager: PID=1624 TID=1816 Further logs for driver related operations can be found in the target operating system at %WINDIR%infsetupapi.offline.log - CDriverManager::Initialize
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Warning DISM DISM Provider Store: PID=1624 TID=1816 Failed to load the provider: X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Transmog Provider: PID=1624 TID=1816 Current image session is [OFFLINE] - CTransmogManager::GetMode
2020-05-17 19:18:34, Info DISM DISM Transmog Provider: PID=1624 TID=1816 Determined WinDir path = [F:Windows] - CTransmogManager::GetWinDirPath
2020-05-17 19:18:34, Info DISM DISM Transmog Provider: PID=1624 TID=1816 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2020-05-17 19:18:34, Info DISM DISM Transmog Provider: PID=1624 TID=1816 Product Type: [WinNT] - CTransmogManager::Initialize
2020-05-17 19:18:34, Info DISM DISM Transmog Provider: PID=1624 TID=1816 Product Type ServerNT : [No] - CTransmogManager::Initialize
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Connecting to the provider located at X:windowsTEMP3ADD0C2B-68A2-4539-8628-E09B7B59F330SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM Provider Store: PID=1624 TID=1816 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-05-17 19:18:34, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2020-05-17 19:18:34, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager
2020-05-17 19:18:34, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
2020-05-17 19:18:34, Info DISM NetAdapter: PID=1624 TID=1816 Setting NetSetup plugin search directory to F:Windowssystem32 - AddNetAdapter::ConnectToOfflineNetSetup
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 PNP device has Hardware Id: PCIVEN_1AF4&DEV_1000&SUBSYS_00011AF4&REV_00 - AddNetAdapter::LoadPnpPropertiesFromHostAdapter
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 PNP device has Location Path: PCIROOT(0)#PCI(0300) - AddNetAdapter::LoadPnpPropertiesFromHostAdapter
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 PNP device has description: Red Hat VirtIO Ethernet Adapter - AddNetAdapter::LoadPnpPropertiesFromHostAdapter
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 PNP device has driver service: netkvm - AddNetAdapter::LoadPnpPropertiesFromHostAdapter
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 Resolved ms_tcpip to 0004-{43504950-0054-0000-4396-f76b563a898a} - AddNetAdapter::GetOfflineDriverByComponentId
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 Resolved ms_tcpip6 to 0004-{50495036-5443-0000-c278-68fd7dfb2873} - AddNetAdapter::GetOfflineDriverByComponentId
2020-05-17 19:18:35, Error DISM NetAdapter: PID=1624 TID=1816 Failed to create the network interface in the offline store - AddNetAdapter::SaveAdapterToOffline(hr:0x80073b01)
2020-05-17 19:18:35, Info DISM NetAdapter: PID=1624 TID=1816 /Add-NetAdapter failed. No changes were made to the system. - AddNetAdapter::Invoke
2020-05-17 19:18:35, Error DISM DISM OfflineSetup Provider: PID=1624 TID=1816 onecorebasentsetupopktoolsdismprovidersofflinesetupproviderdllofflinesetupmanager.cpp:361 - COfflineSetupManager::ExecuteCmdLine(hr:0x80073b01)
2020-05-17 19:18:35, Error DISM DISM.EXE: OfflineSetupManager processed the command line but failed. HRESULT=80073B01
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Package Manager: PID=1624 TID=1816 Finalizing CBS core. - CDISMPackageManager::Finalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-05-17 19:18:35, Info CBS Execution Engine Finalize
2020-05-17 19:18:35, Info CBS Execution Engine Finalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CoreResourcesUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: SessionManagerFinalize
2020-05-17 19:18:35, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:9
2020-05-17 19:18:35, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:8
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: GetPublicObjectMonitor::Audit
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: WcpUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: DrupUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CfgMgr32Unload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: DpxUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CbsEsdUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: CbsEventUnregister
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: AppContainerUnload
2020-05-17 19:18:35, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:35, Info DISM DISM Provider Store: PID=1624 TID=1816 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM OS Provider: PID=1624 TID=1816 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1624 TID=1816 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM Manager: PID=1732 TID=1688 Closing session event handle 0x234 - CDISMManager::CleanupImageSessionEntry
2020-05-17 19:18:37, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2020-05-17 19:18:37, Info DISM DISM.EXE:
2020-05-17 19:18:37, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2020-05-17 19:18:37, Info DISM DISM.EXE:
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2020-05-17 19:18:37, Info DISM DISM Provider Store: PID=1732 TID=1688 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
And here is my iPXE boot script:
Code:
:winpe
dhcp
cpuid --ext 29 && set arch amd64 || set arch x86
set iscsi-server lymiwdsserver
set sanpath iscsi:lymiwdsserver::::iqn.1991-05.com.microsoft:lymiwdsserver-testwindwossystem1-target
sanhook ${sanpath} || goto faild
set root_path http://lymiwinserver5:18081
kernel ${root_path}/wimboot-latest/wimboot-2.6.0-signed/wimboot
initrd ${root_path}/images/winpe/${arch}/media/boot/BCD BCD
initrd ${root_path}/images/winpe/${arch}/media/boot/boot.sdi boot.sdi
initrd ${root_path}/images/winpe/${arch}/media/sources/boot.wim boot.wim
boot
Any help is appreciated!
Everything you need to delete any registry key on your PC
by Matthew Adams
Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things… read more
Updated on December 8, 2022
Reviewed by
Alex Serban
After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more
- If you are getting an error while trying to delete a registry on your PC, it might be because you don’t have the necessary permissions.
- Try editing your Registry key permissions or using a third-party registry manager to fix this issue.
- Another effective and easy solution is to use the RegDelNull file from Sysinternal.
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
- Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
- Click Start Scan to find Windows issues that could be causing PC problems.
- Click Repair All to fix issues affecting your computer’s security and performance
- Restoro has been downloaded by 0 readers this month.
Deleting and editing registry keys isn’t something you should usually do. However, sometimes it is needed to fix a system error.
Yet, some users are met with Cannot delete key: Error while deleting key prompt while trying to delete a locked registry key. This guide will show you how to fix this error on your PC.
Why can I not delete the registry key?
The reasons you are getting an error while deleting a key on Regedit are not far-off. Below are two major ones:
- Lack of permission: Registry keys are treated like files and folders on your PC. So, if Windows 10 is showing an error while deleting a key, it might be because you don’t have permission to delete them. So, the solution here is to take ownership of the keys and try to delete them again.
- Presence of null characters: If the key you are trying to delete contains null keys, you might be unable to delete all specified values. You can fix this by adding RegDelNull to your PC.
How do I fix the Error while deleting key issues?
1. Open the Registry Editor as Administrator
- Press the Windows key and type regedit.
- Select Run as administrator under Registry Editor.
- Now, click the Yes button if you get a UAC prompt.
- Finally, try to delete the keys again.
The first thing to do if you are getting an error while deleting a registry key is to run Registry Editor as an admin. This is because your PC considers registry key deletion highly privileged.
So, you need to have administrative rights to do it.
2. Edit the Registry Key’s Permissions
- Follow the steps in Solution 1 to launch Registry Editor as an admin.
- Right-click the registry key you need to delete and select Permissions…
- Now, click the Advanced button.
- Click the Change link at the top of the window.
- Enter your username in the Enter object name text box.
- Now, click the Check Names button, followed by the OK button.
- From here, click the Apply and OK buttons on the Advanced Security page.
- Go back to the Permissions for page, click your username and check the Allow box before the Full Control option.
- Finally, click the Apply button, followed by OK to save the changes and try to delete the keys again.
If you are getting an error while deleting a registry key, it might be because you don’t have ownership of the key. Following the steps above will give you full control of the keys.
3. Add RegDelNull to Windows
- Download the RegDelNull zip file.
- Open Downloads and right-click the zip file, and select Extract files..
- Now, open the extracted folder and double-click the exe file there.
- Finally, enter the command (replace the key path with the path of the registry key you want to delete ) below and hit Enter:
regdelnull <key path> -s
Another possible reason you are getting an error while deleting a key is the activities of the null characters in the key. The RegDelNull will help replace these null characters and help you delete the key easily.
4. Use PSExec
- Download and install PSExec.
- Press the Windows key, type cmd, and click Run as administrator under Command Prompt.
- Now, type the command below and hit Enter:
psexec -i -d -s c:windowsregedit.exe
- This will now open the Registry Editor. Ensure that you don’t have any prior window of Regedit open.
- Finally, try deleting the keys again.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
If you still get an error while trying to delete a registry key after changing the permission, you need to use PSExec. This has proved effective for many users. So, you should try it too.
- How to Resolve Microsoft Office Error Code 30204-44
- Fix: Microsoft Surface is Overheating [Book, Pro, Laptop]
- How to Disable Xbox Game Bar on Windows 10 [4 ways]
- Error Opening File for Writing: 9 Methods to Fix This Issue
5. Delete the key with Registry DeleteEx
If all the solutions above prove futile in fixing the error while deleting a key prompt, you might need to try an alternative.
One effective program that users have found joy in using is DeleteEx. This tool has a GUI that you can erase locked registry entries.
Furthermore, you can also select to erase all the key’s subkeys. As this software includes more settings, DeleteEx might be a better program for deleting registry entries with than
There you have it: Everything you need to fix the error deleting a key prompt in Windows. Just make sure you follow the instructions carefully, and you should be able to delete your registry keys again.
If you made a mistake and want to know how to undo changes on Registry Editor, check our detailed guide to do it quickly.
Feel free to let us know the solution that worked for you in the comments below.
Newsletter
do you need something like this i found it in the C:WindowsPanther
2019-11-15 10:34:11, Info IBS InstallWindows:Successfully loaded resource language [en-us]
2019-11-15 10:34:11, Info [0x0601c1] IBS InstallWindows:Install Path = X:Sources
2019-11-15 10:34:11, Info [0x0601c2] IBS InstallWindows:Setup Phase = 2
2019-11-15 10:34:11, Info [0x0606cc] IBS LogBootDeviceInfo:The firmware boot device ARC path is [multi(0)disk(0)cdrom(0)] and NT path is [].
2019-11-15 10:34:11, Info [0x0606cc] IBS LogBootDeviceInfo:The system boot device ARC path is [ramdisk(0)] and NT path is [DeviceRamdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}].
2019-11-15 10:34:11, Info [0x0601e9] IBS CheckWinPEVersion:Compatible WinPE Version 10.0.17763 sp 0.0
2019-11-15 10:34:11, Info [0x0601c9] IBS InstallWindows:Starting a new install from WinPE
2019-11-15 10:34:11, Info IBS InstallWindows: Setup working directory = X:windowspanther
2019-11-15 10:34:11, Info [0x0601ce] IBS Setup has started phase 2 at 2019-11-15 10:34:11
2019-11-15 10:34:11, Info [0x0601cf] IBS Install source is X:Sources
2019-11-15 10:34:11, Info [0x0601d0] IBS Build version is 10.0.17763.1 (WinBuild.160101.0800)
2019-11-15 10:34:11, Info [0x06403f] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [X:windowspantherSetupInfo] Setup phase is [2]
2019-11-15 10:34:11, Info [0x090008] PANTHR CBlackboard::Open: X:windowspantherSetupInfo succeeded.
2019-11-15 10:34:11, Info [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [X:windowspantherSetupInfo]
2019-11-15 10:34:11, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [en-us].
2019-11-15 10:34:11, Info IBS InstallWindows:Setup architecture is [x64]
2019-11-15 10:34:11, Info [0x0601d5] IBS InstallWindows:Starting with Empty Queue. Setup Phase = 2
2019-11-15 10:34:11, Info PANTHR InitializedCriticalSection for pExecQueue->csLock;
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ScenarioDetect in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Engine in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Internal in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ErrorHandler in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Diagnostic in diagnostic.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Unattend in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ParseCommandLine in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Ems in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module PrepareInstallDrive in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module TempDrive in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CopySetupFiles in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module BootPrep in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module BootEntries in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CopyPrivates in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ProductKey in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ComputerName in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module License in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module DiskInformation in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module FixBBPaths in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module DiskConfig in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CreatePageFile in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Imaging in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CopyImages in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module DeployImages in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module DiskSpace in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Completion in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module MountDev in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module Cmi in cmisetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module SystemRestore in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module FirstBootCleanup in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module RestartModule in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ExternalDrivers in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CBS in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module SkuAssembly in cmisetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module LanguagePack in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ConfigSet in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module UnattendImgInstall in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module CFGOfflineImage in winsetup.dll
2019-11-15 10:34:11, Info PANTHR InitializeModule: Initializing ExecQueue->csLock;
2019-11-15 10:34:11, Info PnPIBS: Initializing the PnP IBS Module …
And i found this in the setuperr file in the same C:WindowsPanther
2019-11-15 10:35:36, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490]
2019-11-15 10:42:25, Error CBS Failed to load Session:5988_779984 [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
tell if you find it usefull otherwise tell me where to look
I bought an used ThinkPad T520 that came with Windows 7 from the previous owner. So I got it home, installed Linux Mint, and everything went fine, but I think I will need to use Windows. So I created a bootable pendrive and tried to install Windows 10. I managed to boot into the installation, erase the drive, and everything went fine until it had to reboot. When it reboots, it shows the loading icon with the Windows logo, then a window with the message «Windows setup could not configure to run on this computer’s hardware» blinks for half a second and the laptop powers off. I booted from Mint and managed to get these logs:
setuperr.log
2022-06-17 22:55:55, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490]
2022-06-17 23:14:42, Error SYSPRP ActionPlatform::DeleteValue: Error from RegOpenKeyExW on key HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionSetupSysprepOfflineStateSpecialize; dwRet = 0x13
2022-06-17 23:14:42, Error SYSPRP SysprepSession::Execute: Win32 error (19), could not execute actions
2022-06-17 23:14:42, Error SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x13
2022-06-17 23:14:42, Error [0x0f0435] SYSPRP Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x13[gle=0x00000013]
setupact.log
2022-06-17 23:14:42, Info SYSPRP Finished AppxPreRegisterPackage for all packages.
2022-06-17 23:14:42, Info SYSPRP GenerateBytecodeForPackages completed with 0x0.
2022-06-17 23:14:42, Info SYSPRP Exiting AppxSysprepSpecializeOnline with 0x0.
2022-06-17 23:14:42, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'AppxSysprepSpecializeOnline' from C:WindowsSystem32AppxSysprep.dll
2022-06-17 23:14:42, Error SYSPRP ActionPlatform::DeleteValue: Error from RegOpenKeyExW on key HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionSetupSysprepOfflineStateSpecialize; dwRet = 0x13
2022-06-17 23:14:42, Error SYSPRP SysprepSession::Execute: Win32 error (19), could not execute actions
2022-06-17 23:14:42, Error SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x13
2022-06-17 23:14:42, Info SYSPRP Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
2022-06-17 23:14:42, Info SYSPRP Callback_Specialize: Specialize return: [19]
2022-06-17 23:14:42, Warning SYSPRP Callback_Specialize: Couldn't delete InstallDriveTrusted registry value; Error = 0x13.
2022-06-17 23:14:42, Error [0x0f0435] SYSPRP Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x13[gle=0x00000013]
2022-06-17 23:14:42, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [A InstalaE7E3o do Windows nE3o pF4de configurar o Windows para ser executado no hardware do computador.]
I tried searching for some terms found on the logs but couldn’t find any good results. I saw some places saying it’s a driver issue, but I’m not sure how I would update any drivers without an OS. What could possibly be happening here and how can I fix it? I can provide more information if needed. Full logs here
Things I’ve tried:
- Trying to install again (more than 10 times at this point)
- Using Ventoy instead of the Windows Media Creation Tool
- Using Rufus
- Switching SATA mode from AHCI to Compatibility
- Trying to install Home edition instead of Pro
- Physically disabling Wi-Fi
- Using another pendrive
Обновлено 12.06.2017
Добрый день уважаемые читатели сегодня хочу рассказать, как решается ошибка an error occurred while attempting при загрузке Windows. Данная инструкция подойдет как для клиентских операционных систем по типу Windows 7, 8.1 и 10, так и для Windows Server. На исправление данной проблемы у вас уйдет не более 10 минут, даже в случае с сервера это не такой уж и большой простой по времени.
Что ознаает error occurred while attempting to read
И так расскажу, что было у меня. У нас есть блейд корзина с блейдами hs22, у них своих дисков нету и загружаются они по fc с СХД netApp, после аварии на одном из блейдов когда шла загрузка windows server 2008 r2, выскочила вот такая ошибка
An error occurred while attempting to read the boot configuration data
File: EFIMicrosoftBootBCD
status: 0xc000000f
Из ошибки видно, что операционная система не может загрузиться из за загрузчика в файле EFIMicrosoftBootBCD.
Причины ошибки 0xc000000f
- Повредился загрузчик Windows
- Случайно удалили загрузочную область
Таблица разделов загрузочного жесткого диска с UEFI GPT
У вас должны быть по крайней мере три раздела.
- Системный раздел EFI (ESP – EFI System Partition) – 100 Мб (тип раздела — EFI)
- Резервный раздел Майкрософт – 128 Мб (тип раздела — MSR)
- Основной раздел Windows – раздел с Windows
Или еще есть дополнительный раздел.
- Windows RE
Давайте поговорим теперь о каждом из них более подробно.
Windows RE
Windows RE это раздел 300 Мб на разделе GPT, и смысл его в том, чтобы содержать данные для восстановления загрузчика. Такой же есть и в системах с разметкой MBR, размером 350 Мб, он еще носит название System Reserved и наряду с RE содержит файлы, необходимые для загрузки Windows.
Среда восстановления находится в файле winre.wim
Windows RE создается в процессе установки Windows.
- В процессе создания структуры разделов для Windows RE назначается специальный атрибут 0x8000000000000001. Он является комбинацией двух атрибутов – один блокирует автоматическое назначение буквы диска, а другой – помечает раздел как обязательный для работы системы, что препятствует его удалению из оснастки управления дисками.
- К разделу Windows применяется образ системы — стандартный install.wim или настроенный custom.wim. Как следствие, winre.wim оказывается в папке WindowsSystem32Recovery.
- На разделе Windows RE создается папка RecoveryWindowsRE, после чего это расположение среды восстановления регистрируется утилитой reagentc.
W:WindowsSystem32reagentc.exe /setreimage /path T:RecoveryWindowsRE /target W:Windows
reagentc.exe входит в состав Windows и запускается она именно с раздела операционной системы. Наряду с регистрацией RE команда перемещает winre.wim с раздела Windows на служебный раздел Windows RE. Если вы хотите увидеть файл, сначала назначьте диску букву с помощью утилиты diskpart. Поскольку файл имеет атрибуты системный и скрытый, быстрее всего его покажет команда dir /ah.
В результате этих действий загрузка в среду восстановления происходит с раздела Windows RE. Подробности процесса я покажу в грядущем рассказе о восстановлении резервной копии.
Раздел Windows RE не является обязательным для работы Windows. Среда восстановления может отсутствовать или находиться прямо на разделе с операционной системой. Однако размещение Windows RE на отдельном разделе преследует две цели:
- Загрузка в среду восстановления на ПК с зашифрованным разделом Windows. В среду восстановления невозможно загрузиться, если она находится на разделе с Windows, который зашифрован. Раздел Windows RE исключен из шифрования, поэтому всегда можно попасть в среду и воспользоваться ее инструментами.
- Защита среды восстановления от шаловливых рук. Поскольку раздел невозможно удалить в оснастке управления дисками, вероятность его смерти по неосторожности несколько ниже, хотя при желании его несложно удалить с помощью diskpart.
Раздел System (EFI)
Раздел EFI, отформатированный в FAT32, является обязательным для разметки GPT на системах с UEFI. Стандартный размер раздела EFI составляет 100MB, но на дисках расширенного формата 4K Native (секторы 4KB) он увеличен до 260MB ввиду ограничений FAT32. Изготовители ПК могут хранить на этом разделе какие-то свои инструменты, поэтому его размер варьируется в зависимости от производителя.
В разметке GPT раздел EFI выполняет одну из ролей, которая возложена на раздел System Reserved в разметке MBR. Он содержит хранилище конфигурации загрузки (BCD) и файлы, необходимые для загрузки операционной системы.
Раздел MSR (Microsoft System Reserved)
Этот раздел также является обязательным для разметки GPT. Он отформатирован в NTFS и занимает в Windows 8 и 8.1 — 128MB, а в Windows 10 — 16MB. GPT не позволяет использовать скрытые секторы диска (в отличие от MBR), поэтому раздел MSR необходим для служебных операций встроенного и стороннего ПО (например, конвертирование простого диска в динамический).
Несмотря на наличие “System Reserved” в названии, раздел MSR не имеет ничего общего с разделом System Reserved в разметке MBR. Кроме того, он не виден в файловых менеджерах и оснастке управления дисками, хотя diskpart его показывает.
Раздел Windows
Это раздел с операционной системой, к которому применяется стандартный образ install.wim или настроенный образ.
Устраняем error occurred while attempting to read
Как вы помните мы с вами словили вот такую вещь
An error occurred while attempting to read the boot configuration data
File: EFIMicrosoftBootBCD
status: 0xc000000f
Теперь давайте разберемся как с графическими методам так и с методами командной строки.
Утилитой восстановление только для клиентский Windows
Тут мы будем пользоваться точками восстановления Windows, они по умолчанию включены в клиентские Windows 7, 8.1, 10, и это логично, чтобы быстро восстановиться при каких то глюках системы. Тут нам понадобится загрузочная флешка с такой же версией Windows, если у вас например WIndows 8.1 64x то и на флешке должна быть 64 битная версия.
Для Windows 7, это выглядит так
Начав загружать дистрибутив Windows 7 с загрузочной флешки, у вас появится окно установки, в нижнем углу нажмите Восстановление системы.
У вас появятся параметры, самый первый вариант это выбрать Восстановление запуска
Буде выполнена попытка восстановить загрузочные области Windows 7
Жмем Исправить и перезагрузить.
Если после перезагрузки, у вас осталась ошибка, то снова заходим в данное меню и выбираем уже тогда второй пункт, Восстановление системы Windows 7. Утилита найдет установленную операционную и попытается откатить ее на момент когда она работала корректно, ваши персональные данные не пострадают, максимум вы можете не досчитаться программ.
Для Windows 8.1 и 10, это выглядит так
Ошибка an error occurred while attempting при загрузке решается так же, вы создаете загрузочную флешку с Windows 8.1, как это сделать ссылка выше. Загружаетесь с нее и вы попадаете в среду восстановления. Так же на окне установки, нажимаете восстановление системы.
Поиск и устранение неисправностей > 1 вариант Вернуть компьютер в исходное состояние, с сохранением файлов и второй вариант Дополнительные параметры > Восстановление системы или восстановление образа системы.
После перезагрузки, у вас должно быть все отлично, в это преимущество десктопных платформ, от серверных Windows Server, так как в серверных версиях, по умолчанию все отключено и администратору нужно все включать самому, а отключено из за экономии ресурсов, но с моей точки зрения могли бы для точек восстановления сделать исключение.
Восстановление для всех через командную строку
Данный метод, более сложный, особенно для тех кто в первый раз видит командную строку операционной системы. Данный метод подойдет как и для 7,8.1,10 так и для Windows Server 2008 R2 и 2012 R2. В данном методе вам так же потребуется загрузочная флешка с нужным дистрибутивом вашей ос. Я буду показывать на примере Windows Server 2008 r2, но все действия как я и писал подойдут для любой ос, начиная с W7.
Еще единственное отступление, что если у вас как и у меня операционная система накрылась на блейд сервере, то сделайте первый пункт, если у вас обычный ПК, то просто его пропустите.
1 Часть только для blade servers
- Так как у меня блейд система, то для того чтобы туда подгрузить дистрибутив для ремонта, потребуется подмантировать ISO образ, делает это просто. Заходите в Blade Center, выбираете Remote control и через java KVM выбираете нужный блейд. Сверху нажимаете Remote Drive > Select Image
Указываем путь до нашего ISO
Выбираем сверху нужный блейд для монтирования и ставим галку защиты от записи Write Protect, после чего Mount All.
Все видим ISO смонтирован, закрываем данное окно.
Теперь в Boot меню выбираем загрузка с DVD Rom. В итоге начнется загрузка с вашего ISO, вставленного в Virtual CD-rom.
2 часть для всех
Вы увидите, стандартную полосу загрузки.
У вас появится окно выбора языка
Если у вас дистрибутив английский, то для открытия командной строки нажмите Shift+F10, если русская, то выберите раскладку клавиатуры США международная, так как дальнейшие команды будут вводиться именно на этой раскладке, жмем далее
Раскладку выбрали на следующем окне жмем привычное меню восстановление.
В серверной ос, как я вам и говорил вы не увидите, контрольных точек. Выбираем второй пункт и далее.
И вот она долгожданная командная строка
В Windows 8.1, 10 и Server 2012 R2, попасть в командную строку можно так же, но меню слегка видоизменили. Вы так же идете в восстановление, потом диагностика.
Далее Дополнительные параметры > Командная строка.
И вот тут мы сейчас рассмотрим несколько методов.
1 метод устранить an error occurred while attempting
В первом методе мы с вами выполним две команды, восстанавливающие загрузочную область. Мы используем команду Bootrec. Введите ее в командной строке, вам отобразиться перечень атрибутов.
- /FixMbr > восстановит MBR запись, с UEFI это не прокатит
- /FixBoot > делает новую запись в системный раздел
- /ScanOs > поиск всех Windows на дисках
- >rebuildBcd > сканирование всех ос и добавление из в загрузочное меню
Выполним Bootrec.exe /FixMbr, потом Bootrec.exe /FixBoot
Обе команды штатно отработали, в первый сектор загрузочного раздела записана новая загрузочная запись, а вторая команда записывает новый загрузочный сектор. Пишем Exit и перезагружаемся.
2 метод устранить an error occurred while attempting
Если первый метод вам не помог, не спешите расстраиваться, так же загружаемся в командную строку и вводим вот такие команды.
Bootrec /ScanOs, она просканирует все ваши жёсткие диски и разделы на наличие операционных систем и если такие будут найдены, то выйдет соответствующее предупреждение. Затем нужно ввести команду Bootrec.exe /RebuildBcd, данная утилита предложит внести найденные Windows в меню загрузки, соглашаемся и вводим Y и жмём Enter, всё найденная Windows добавлена в меню загрузки
еще в дополнение можно тут же прописать bootsect /NT60 SYS , но если у вас UEFI, то получите ошибку.
Если все ок, то получите обновленную область bootcode,
Перезагражаемся и радуемся жизни. Ниже способы для UEFI.
3 метод устранить an error occurred while attempting для UEFI
Идем дальше в нашей эпопеи и разберем слегка может быть сложный метод для новичков, но зато он поможет восстановить загрузку UEFI.
Так же загружаемся в режим командной строки и вводим
Так же загружаемся в режим командной строки и вводим
diskpart
list disk > ей смотрим список разделов в системе
Выберем диск, на котором установлена Windows 8 (если жесткий диск в системе один, его индекс будет нулевым):
sel disk 0
Выведем список разделов в системе:
list vol
В нашем примере видно, что раздел EFI (его можно определить по размеру 100 Мб и файловой системе FAT32) имеет индекс volume 1, а загрузочный раздел с установленной Windows 8.1 — volume 3.
Назначим скрытому EFI разделу произвольную букву диска:
select volume 1
assign letter M:
Завершаем работу с diskpart:
exit
Перейдем в каталог с загрузчиком на скрытом раздел
cd /d m:efimicrosoftboot
Пересоздадим загрузочный сектор: на загрузочном разделе
bootrec /fixboot
Удалим текущий файл с конфигурацией BCD, переименовав его (сохранив старую конфигурацию в качестве резервной копии):
ren BCD BCD.bak
С помощью утилиты bcdboot.exe пересоздадим хранилище BCD, скопировав файлы среды загрузки из системного каталога:
bcdboot C:Windows /l en-us /s M: /f ALL
где, C:Windows – путь к каталогу с установленной Windows 8.1.
/f ALL – означает что необходимо скопировать файлы среды загрузки, включая файлы для компьютеров с UEFI или BIOS (теоретическая возможность загружаться на EFI и BIOS системах)
/l en-us — тип системной локали . По умолчанию используется en-us — английский язык (США) .
В случае использования русской версии Windows 8.1 команда будет другая:
bcdboot C:Windows /L ru-ru /S M: /F ALL
Вот как выглядит структура на самом деле
4 метод устранить an error occurred while attempting для UEFI
Идем дальше в нашей эпопеи и разберем слегка может быть сложный метод для новичков, но зато он поможет восстановить загрузку UEFI.
Так же загружаемся в режим командной строки и вводим
diskpart
list disk > ей смотрим список разделов в системе
у меня операционная система стоит на 100 гиговом диске с буквой С.
Командой list disk мы посмотрим список дисков
Меня интересует Диск 0, так как на нем система. Выберем его.
List partition > Выводим список разделов
Select partition 1 > Выбираем нужный с загрузчиком (Если есть системный то его, если его нет то Зарегистрированный) Все равно их удалять оба
Убиваем первый и второй раздел (Системный и зарегистрирован)
Delete partition override
Снова введем List partition и убедимся что оба удалились. Теперь мы можем вручную пересоздать разделы EFI и MSR. Для этого в контексте утилиты diskpart последовательно выполните команды
Выбираем диск
select disk 0
create partition efi size=100
Убеждаемся, что выбран раздел 100 Мб (звездочка)
list partition
select partition 1
format quick fs=fat32 label=»System»
assign letter=G
create partition msr size=128
list partition
list vol
Все успешно создалось.
В нашем случае разделу с Windows уже назначена буква диска C:, если это не так, назначим ему букву следующим образом
select vol 8
assign letter=G
exit
Скопируем файлы среды EFI из каталога установленной Windows 2008 R2 у вас другая может быть:
mkdir G:EFIMicrosoftBoot
xcopy /s C:WindowsBootEFI*.* G:EFIMicrosoftBoot
Идем на следующий пункт решения ошибки an error occurred while attempting
Пересоздадим конфигурацию загрузчика Windows Server 2008 R2:
g:
cd EFIMicrosoftBoot
bcdedit /createstore BCD
bcdedit /store BCD /create {bootmgr} /d “Windows Boot Manager”
bcdedit /store BCD /create /d “Windows Server 2008 r2” /application osloader
Команда возвращает GUID созданной записи, в следующей команде этот GUID нужно подставить вместо {your_guid}
bcdedit /store BCD /set {bootmgr} default {your_guid}
bcdedit /store BCD /set {bootmgr} path EFIMicrosoftBootbootmgfw.efi
bcdedit /store BCD /set {bootmgr} displayorder {default}
Дальнейшие команды выполняются в контексте {default}
bcdedit /store BCD /set {default} device partition=c:
bcdedit /store BCD /set {default} osdevice partition=c:
bcdedit /store BCD /set {default} path WindowsSystem32winload.efi
bcdedit /store BCD /set {default} systemroot Windows
exit
Все перезагружаемся и пробуем запустить ваш компьютер или сервер. Еще варианты.
- Отключаем питание ПК
- Отключаем (физически) жесткий диск
- Включаем ПК, дожидаемся появления окна с ошибкой загрузки и снова его выключаем.
- Подключаем диск обратно
5 метод устранить an error occurred while attempting
Есть еще метод для решения ошибки an error occurred while attempting и 0xc000000f, и это софт Acronis Disk Director. Есть такой загрузочный диск Acronis Disk Director для ремонта, есть ноутбук с двумя ос, первая Windows7, а вторая Windows 8.1, и обе не грузятся, загружаемся с нашего Acronis Disk Director
Все надеюсь у вас теперь ушла ошибка an error occurred while attempting при загрузке Windows и вы загрузились. ошибка в том, что у нас на обоих жёстких дисках должны быть отмечены красным флажком первые скрытые разделы System Reserved (Зарезервировано системой). На Windows 7 объём такого раздела составляет 100 МБ, а на Windows 8 350 МБ, именно эти разделы носят атрибуты: Система. Активнен и именно на этих разделах находятся файлы конфигурации хранилища загрузки (BCD) и файл менеджера загрузки системы (файл bootmgr). А у нас получается эти атрибуты носят другие разделы. Из-за этого Windows 7 и Windows 8.1 не загружаются.
Выбираем первый жёсткий Диск 1, щёлкаем на первом разделе System Reserved (Зарезервировано системой) правой мышью и выбираем «Отметить как активный»
Том Зарезервировано системой будет отмечен как активный. Нажимаем ОК.
То же самое делаем с Диском 2. Программа Acronis Disk Director работает в режиме отложенной операции, чтобы изменения вступили в силу нажимаем кнопку «Применить ожидающие операции»
Продолжить. Как видим, после наших изменений активными стали те разделы которые нужно.
Надеюсь вам удалось устранить ошибки an error occurred while attempting и 0xc000000f