Try to initialize panther logging 1 times last error 0x0

Try to initialize panther logging 1 times last error 0x0

I’m not sure if this is the best place to ask, but I figured I’d give it a shot, as I have spent DAYS trying to get my drive to boot so I can properly take an image or do a «repair upgrade»

I recently built a brand new PC because my old motherboard from 2012 took a dump. I thought getting the data from my old Intel 240gb SSD would be no problem, but it has proved to be the most challenging ever. I have SO many hours into this, googling issues, error codes, trying different software, boot disks, recovery USB’s, repairs, etc. When I plug the drive into my new system, via SATA to USB or just directly SATA to motherboard, I can see the data on the drive, but I just can’t get it to boot. I have tried everything. dism, (component store cannot be repaired), sfc, chkdsk (chkdsk says the drive is 100% healthy, no bad sectors), etc. I have tried taking an image of the drive / windows partition with Macrium and AOMEI backupper and it successfully takes the image, but when I try to restore to my new SSD (1TB NVME) I run into the same boot issues. It is not a UEFI vs Legacy BIOS issue, as my old mobo was UEFI and AHCI as well, not IDE. I’ve done all of the troubleshooting I could find on the web, googled every error message, messed with diskpart, with bootrec rebuildbcd, bootrec fixboot commands, etc. I suspect maybe some sort of corruption has happened with windows system files, or the registry, OR it has something to do with my new drive being GPT and this old source drive being MBR. I feel I have tried EVERYTHING on my own, and usually tech issues are no problem for me.

I REALLY don’t want to start over, as I have years worth of settings, customizations, programs, app data, user data, etc on the SSD, and I know you can’t just simply copy and paste the Windows or the Users directory into a new installation of win10 without all hell breaking loose.

My ultimate goal is to get this drive booting properly so that I can properly image it / clone it to my new NVME SSD in my new machine so that all of my user data, software, customizations, app data, etc are on the new system, as if nothing changed except for much better and faster hardware.

So here is the closest I’ve gotten to figuring the issue out before I hit dead ends. I’ve googled every error code and every log file entry from DISM I find pertinent. I suspect my windows image component store is messed up and/or my registry, but there’s GOT to be a way to fix it. I have uploaded the commands and the responses I got, as well as the log files they generated.
Here is what I get when I do dism /checkhealth

Here is what I get when I attempt sfc with any parameters as well:

«Windows Resource Protection could not perform the requested operation.» (No log file)

Here is what I get when I try to restore the image with the .esd file windows media creation tool provides:

I have triple-checked the commands to make sure my syntax is correct and that all of the paths, drive letters, etc are all correct and the files exist. From here, I’m not really sure what to do or if it’s even possible to get dism to play nice and repair the «component store» (which I have no idea what it is)

Also, I forgot to mention. Everything on my old system appeared to be working fine last week. This all started when I attempted to put my new graphics card (MSI RTX 2060) into the system. This is when all hell broke loose. I have no idea if that is what caused all of this, and if so, HOW. or if it’s just a complete coincidence. Previously I had an old ass GTX 560 TI, so quite a bit newer graphics card but I still for the life of me can’t figure out how in the world this could cause windows to be messed up to the point of not booting and have it’s «component store» corrupted / unrepairable. Alternatively, I suppose it could have been a windows update to mess everything up.

Am I completely screwed if DISM tells me «the component store cannot be repaired»? Or do I still have options? There’s a LOT of stuff in those log files, that maybe if I could fix them, I could get dism to play nice and fix the component store and then hopefully boot back up? I have tried doing all of the windows USB repair / startup repair with no luck. The furthest I’ve gotten to is getting it to the spinning dots of «attempting repairs» and it just stays stuck that way forever. I feel I’m SO CLOSE to fixing this issue, because all of my files are there, I just need to get it to boot and then moved over to my new system so all of my data and settings and software remain in place.

Do I have any options?

Thank you SO MUCH for any help / suggestions. My computer is my livelihood and how I put food on the table, and it’s very hard to work and be productive without all of my data / software, etc.

I read the forum rules and here are my results for 2-5

2) when I try to run sfc, I always get: «Windows Resource Protection could not perform the requested operation.»

3) I have attached my DISM logs and results via pastebin above.

4) When I attempt to run SFCFix (From a USB Windows PE environment because I cannot boot) I get the following error: «The program can’t start because msdelta.dll is missing from your computer.» — Is this problem related? Or can SFCFix only be ran from NON-USB environments? I cannot boot into my Win10 installation or else I would run it that way.

5) I have attached the CBS.zip — One from the C drive which is my main Windows install that has failed to boot (As you can see the last log entries are from 12/02) and then also attached my CBS log from the X drive which is the windows USB rescue environment.

I hope this is enough info to help give you Windows gurus a clue as to what happened. I’m fairly technical and this stuff is way over my head. Thank you all SO MUCH.

Источник

unable to remove windows feature

I’m try to remove the windows defender from all servers but its failing on some servers when running the dism tool.

Dism /online /Disable-Feature /FeatureName:Windows Defender

2019-08-16 10:43:49, Info DISM Try to initialize Panther logging 1 times, last error: 0x0
2019-08-16 10:43:49, Info DISM PID=10740 TID=4768 Successfully loaded the ImageSession at «C:WINDOWSSystem32Dism» — CDISMManager::LoadLocalImageSession
2019-08-16 10:43:49, Info DISM Try to initialize Panther logging 1 times, last error: 0x0
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeLogger
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Provider has previously been initialized. Returning the existing instance. — CDISMProviderStore::Internal_GetProvider
2019-08-16 10:43:49, Info DISM Try to initialize Panther logging 1 times, last error: 0x0
2019-08-16 10:43:49, Info DISM DISM Provider Store: PID=10740 TID=4768 Getting Provider DISMLogger — CDISMProviderStore::GetProvider

2019-08-16 10:43:56, Info DISM DISM Package Manager: PID=13212 TID=13368 Error in operation: (null) (CBS HRESULT=0x80073701) — CCbsConUIHandler::Error
2019-08-16 10:43:59, Error DISM DISM Package Manager: PID=13212 TID=13824 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x80073701)
2019-08-16 10:43:59, Error DISM DISM Package Manager: PID=13212 TID=13824 Failed processing package changes — CDISMPackageManager::ProcessChanges(hr:0x80073701)
2019-08-16 10:43:59, Error DISM DISM Package Manager: PID=13212 TID=13824 Failed ProcessChanges. — CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x80073701)
2019-08-16 10:43:59, Error DISM DISM Package Manager: PID=13212 TID=13824 Failed while processing command disable-feature. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073701)
2019-08-16 10:43:59, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073701

2019-08-16 10:46:09, Info DISM Try to initialize Panther logging 1 times, last error: 0x0
2019-08-16 10:46:09, Info DISM PID=5560 TID=6848 Successfully loaded the ImageSession at «C:WINDOWSSYSTEM32Dism» — CDISMManager::LoadLocalImageSession
2019-08-16 10:46:09, Info DISM Try to initialize Panther logging 1 times, last error: 0x0
2019-08-16 10:46:09, Info DISM DISM Provider Store: PID=5560 TID=6848 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeLogger
2019-08-16 10:46:09, Info DISM DISM Provider Store: PID=5560 TID=6848 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
2019-08-16 10:46:09, Info DISM DISM Provider Store: PID=5560 TID=6848 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
2019-08-16 10:46:09, Info DISM DISM Provider Store: PID=5560 TID=6848 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
2019-08-16 10:46:09, Info DISM DISM Provider Store: PID=5560 TID=6848 Provider has previously been initialized. Returning the existing instance. — CDISMProviderStore::Internal_GetProvider
2019-08-16 10:46:09, Info DISM Try to initialize Panther logging 1 times, last error: 0x0

Источник

DISM / SmartComponentCleanup / HealthRestore not working

#1 Apollo767

Hi, trying to lean up and clean up my windows a bit and running into some issues with all of the mentioned commands (they all stop at random points and throw an error)

SFCFix and CBS (DISM++) log bellow, any help and pointers would be much appreciated! :-)))

I can perform glorified monkey tasks but understanding these logs is beyond me

Windows 10 Version 1607 (OS Build 14393.1480)

Side note: there seem to be no infections in the system (avast, malwarebytes, emsisoft emergency kit scanner)

Edited by Apollo767, 17 February 2021 — 07:55 PM.

BC AdBot (Login to Remove)

• 
• BleepingComputer.com
• Register to remove ads

#2 pcpunk

It’s all gibberish to me! Did you run it as Admin?

Why are you still running » Windows 10 Version 1607″ ?

What’s wrong with the computer?

What is the computer model?

If I don’t reply right away it’s because I’m waiting for Windows 10 to Update.

#3 Apollo767

Hi, thanks a lot for the response

It’s all gibberish to me! Did you run it as Admin?

I am an idiot and I have not (not that it would seem to make a difference in results, I have ran both again as admin and updated the logs

Why are you still running « Windows 10 Version 1607″ ?

I have previously tried to put together a working, updated version. That being said, whenever I did do a clean install and subsequently ran updates it slowed the computer down significantly, so at some point I just gave

up, did a clean install and been running it without much issues since.

What’s wrong with the computer?

The system disk is bloated, especially WinSxS etc. is taking up a lot of space, I was trying to clean it up by running smartcomponentcleanup etc. which kept throwing an error

subsequently I’ve tried to run healthcheck and restore, restore keeps throwing an error also.

What is the computer model?
Toshiba Portege Z30-A-15M, it’s old but being the top spec version at the time it still runs really well for what I need it for

#4 pcpunk

Those commands are not going to clean up your computer.

How big is WinSxS?

I don’t suggest using such an old OS! 10 has gotten a little better since then. Do a Clean Install of 20H2 and if possible Delete all old partitions, but make sure you have all your files and product keys backed up.

This is how you run the tools to repair corrupt or missing system files.

Run DISM as Administrator to Repair the Image. Make sure to be connected to the Internet:

Click on Menu and type cmd or Command, when the Command Prompt comes up right click on it and choose Run as administrator

Copy Paste the below command and press Enter

Then run the System File Checker the same way

It may take an hour or so to run so be prepared. Do not stop it till it finishes.

If sfc /scannow finds errors run it two more times to make sure they are repaired.

If I don’t reply right away it’s because I’m waiting for Windows 10 to Update.

#5 pcpunk

Sorry, I’m not familiar with this command.

If I don’t reply right away it’s because I’m waiting for Windows 10 to Update.

#6 jenae

Hi, back up all your data and do a clean install of windows ten, when finished DO not use Avast (Russian spyware) use only Microsoft Defender it’s all you need , there is no other solution to the problem you have created for yourself.

Edited by jenae, 18 February 2021 — 04:51 AM.

#7 Apollo767

Why do you think Avast is a Russian spyware?

Evidence to support this would be greatly appreciated.

Edit: I’ve read up on this and it would indeed appear they have been selling user data for users running their web extension and the free version of the av

From what I understand however, users could opt in or opt out of this and the practice has been since shut down.

Hi, back up all your data and do a clean install of windows ten, when finished DO not use Avast (Russian spyware) use only Microsoft Defender it’s all you need , there is no other solution to the problem you have created for yourself.

Edited by Apollo767, 18 February 2021 — 06:44 AM.

#8 Apollo767

Those commands are not going to clean up your computer.

Yes, I know, they’re meant to fix the errors which might be what is preventing me from running the component cleanup

How big is WinSxS?

I don’t suggest using such an old OS! 10 has gotten a little better since then. Do a Clean Install of 20H2 and if possible Delete all old partitions, but make sure you have all your files and product keys backed up.

I would like to avoid this, I will have to spend an entire day chopping the whole system down and cleaning the registers afterwards which is a pain. (my current win10 is cleaned down to essentially look and work like win7)

This is how you run the tools to repair corrupt or missing system files.

Run DISM as Administrator to Repair the Image. Make sure to be connected to the Internet:

Click on Menu and type cmd or Command, when the Command Prompt comes up right click on it and choose Run as administrator

Copy Paste the below command and press Enter

Источник

EDIT Note: Apologize for formatting, trying to clean it up.

Hello, I’ve taken over for a former tech that was running SCCM on Server 2012r2 verison 5.00.8412.1003. I’m attempting to learn but still a novice with it. I’m attempting to update the boot image but get this error:

Error: The wizard detected the following problems when updating the boot image.

• Failed to install required components into the boot image The SMS Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus

• Description = «Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)»;

• ErrorCode = 2152205056;

• File = «e:cm1606_rtmsmssiteserversdk_providersmsprovsspbootimagepackage.cpp»;

• Line = 5004;

• ObjectInfo = «CSspBootImagePackage::PreRefreshPkgSrcHook»;

• Operation = «ExecMethod»;

• ParameterInfo = «SMS_BootImagePackage.PackageID=»R5D00025″»;

• ProviderName = «WinMgmt»;

• StatusCode = 2147749889;

We have a huge backlog of drivers it’s attempting to add, I’ve attempted to remove some of the more recent ones to see if that might help but I still have a long list of drivers to remove and was hoping to hold back as to break the ability to image current machines. So I did some additional research and found that I should check SMSProv.log. After some frustration, I found the logging service wasn’t running and creating the file. So I was able to get that up and working. Below is the first error I found after the error message above:

ERROR> Error -2146498530 returned to execute the command line: «C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsamd64DISMdism.exe» /Image:»C:WindowsTEMPBootImages{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}mount» /Add-Package /PackagePath:»C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentamd64WinPE_OCsWinPE-Scripting.cab» SMS Provider 7/12/2018 9:44:11 AM 11332 (0x2C44) Failed to install required components into the boot image C:WindowsTEMPBootImages{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}mount SMS Provider 7/12/2018 9:44:11 AM 11332 (0x2C44)

Before that, I also found this but it appears to continue on:

Error setting property (TransformAnalysisDate) 0x80041002! SMS Provider 7/12/2018 9:43:50 AM 11332 (0x2C44) Error setting property (TransformReadiness) 0x80041002! SMS Provider 7/12/2018 9:43:50 AM 11332 (0x2C44)

So for the DISM.exe error, I went and checked the log file and found these errors reference:

• 2018-07-12 09:44:07, Info DISM Try to initialize Panther logging 1 times, last error: 0x0

• 2018-07-12 09:44:07, Info DISM Try to initialize Panther logging 1 times, last error: 0x0

• 2018-07-12 09:44:07, Info DISM DISM Provider Store: PID=8232 TID=3892 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect

• 2018-07-12 09:44:07, Info DISM Try to initialize Panther logging 1 times, last error: 0x0 2018-07-12 09:44:07, Warning DISM DISM Provider Store: PID=8232 TID=3892 Failed to Load the provider: C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsamd64DISMSiloedPackageProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Info CBS Failed to find a matching version for servicing stack: C:WindowsTEMPBootImages{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}mountWindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.0_none_95e4f9a171a1ad95 [HRESULT = 0x80070490 — ERROR_NOT_FOUND]

• 2018-07-12 09:44:11, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 — ERROR_NOT_FOUND]

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4MsiProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4IBSProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to get the IDismObject Interface — CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4Wow64provider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4EmbeddedProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4AppxProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4AssocProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Warning DISM DISM Provider Store: PID=13444 TID=12916 Failed to Load the provider: C:WindowsTEMPB0B0FB2D-448C-4075-BD87-FC5E38F6DAD4TransmogProvider.dll. — CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

• 2018-07-12 09:44:11, Info DPX Extraction of file: update.ses failed because it is not present in the container (?C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentamd64WinPE_OCsWinPE-Scripting.cab).

• 2018-07-12 09:44:11, Info CBS Not able to add file to extract: update.ses [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]

• 2018-07-12 09:44:11, Error DISM DISM Package Manager: PID=13444 TID=12916 The package WinPE-Scripting-Package is not applicable to the image. — CPackageManagerCLIHandler::Private_ProcessPackageChange

• 2018-07-12 09:44:11, Info DISM DISM Package Manager: PID=13444 TID=13476 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) — CCbsConUIHandler::Error

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED] 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = * 0x80070005 — E_ACCESSDENIED] 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/DRIVERS, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{CD3AE80F-EAEB-4876-B431-0EC1981DFF7E}/mount/Users/Default/ntuser.dat, the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]

• 2018-07-12 09:44:11, Error DISM DISM Package Manager: PID=13444 TID=12916 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)

I attempted to do some research and found few things referencing a possible permissions issue but I went through and made sure the system had full access to the folder. I also have 70 Gigs free on my C drive and 240 on my E drive which I believe should be enough.

Any assistance/idea’s on what to do next would appreciated it. If clearing all the drivers it lists out of the server will fix it, I’ll do it but from the error message, I feel like that’s not the case? I do have a backup of the server in case I brick it. I’ll update my information if I make any changes or discover anything.

Thank you for your time reading this!

var a = @"Dism.exe";
var aa = @"/Mount-Image/ ImageFile:z:_imagesinstall.wim /Index:1 /mountdir:z:_images_test2";
Process.Start(a, aa);

2016-09-02 22:29:03, Info DISM PID=2880 TID=5308
Scratch directory set to ‘C:UserszAppDataLocalTemp’. —
CDISMManager::put_ScratchDir 2016-09-02 22:29:03, Info
DISM PID=2880 TID=5308 DismCore.dll version: 10.0.14393.0 —
CDISMManager::FinalConstruct 2016-09-02 22:29:03, Info
DISM Try to initialize Panther logging 1 times, last error: 0x0
2016-09-02 22:29:03, Info DISM PID=2880 TID=5308
Successfully loaded the ImageSession at «C:WindowsSystem32Dism» —
CDISMManager::LoadLocalImageSession 2016-09-02 22:29:03, Info
DISM Try to initialize Panther logging 1 times, last error: 0x0
2016-09-02 22:29:03, Info DISM DISM Provider Store:
PID=2880 TID=5308 Found and Initialized the DISM Logger. —
CDISMProviderStore::Internal_InitializeLogger 2016-09-02 22:29:03,
Info DISM DISM Provider Store: PID=2880 TID=5308
Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
2016-09-02 22:29:03, Info DISM DISM Provider Store:
PID=2880 TID=5308 Finished initializing the Provider Map. —
CDISMProviderStore::Final_OnConnect 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Getting Provider
DISMLogger — CDISMProviderStore::GetProvider 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Provider has previously
been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider 2016-09-02 22:29:03, Info
DISM Try to initialize Panther logging 1 times, last error: 0x0
2016-09-02 22:29:03, Info DISM DISM Provider Store:
PID=2880 TID=5308 Getting Provider DISMLogger —
CDISMProviderStore::GetProvider 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Provider has previously
been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider 2016-09-02 22:29:03, Info
DISM DISM Manager: PID=2880 TID=5308 Successfully created the local
image session and provider store. —
CDISMManager::CreateLocalImageSession 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Getting Provider
DISMLogger — CDISMProviderStore::GetProvider 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Provider has previously
been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider 2016-09-02 22:29:03, Info
DISM DISM.EXE: 2016-09-02 22:29:03, Info DISM
DISM.EXE: <—— Starting Dism.exe session ——> 2016-09-02 22:29:03,
Info DISM DISM.EXE: 2016-09-02 22:29:03, Info
DISM DISM.EXE: Host machine information: OS Version=10.0.14393,
Running architecture=x86, Number of processors=1 2016-09-02 22:29:03,
Error DISM DISM.EXE: Failed validating command line:
«C:WindowsSystem32Dism.exe» /Mount-Image/
ImageFile:z:_imagesinstall.wim /Index:1 /mountdir:z:_images_test2
2016-09-02 22:29:03, Info DISM DISM.EXE: Image
session has been closed. Reboot required=no. 2016-09-02 22:29:03, Info
DISM DISM.EXE: 2016-09-02 22:29:03, Info DISM
DISM.EXE: <—— Ending Dism.exe session ——> 2016-09-02 22:29:03,
Info DISM DISM.EXE: 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Found the OSServices.
Waiting to finalize it until all other providers are unloaded. —
CDISMProviderStore::Final_OnDisconnect 2016-09-02 22:29:03, Info
DISM DISM Provider Store: PID=2880 TID=5308 Releasing the local
reference to DISMLogger. Stop logging. —
CDISMProviderStore::Internal_DisconnectProvider

Для проверки целостности системных файлов и восстановления поврежденных файлов (библиотек) компонентов в Windows (Windows Server) можно использовать команды SFC и DISM. Эти две утилиты могут быть крайне полезными, если операционная система Windows работает нестабильно, появляются ошибки при запуске стандартных приложений или служб, после вирусного заражения и т.д.

В этой статье мы рассмотрим, как использовать команды
sfc /scannow
,
DISM /Online /Cleanup-Image /RestoreHealth
или
Repair-WindowsImage -Online -RestoreHealth
для восстановления образа и системных фалов в Windows 10/11 и Windows Server 2022/2019/2016.

SFC /scannow: восстановление системных файлов Windows

Перед тем, как восстанавливать образ Windows с помощью DISM, рекомендуется сначала попробовать проверить целостность системных файлов с помощью утилиты SFC (System File Checker). Команда
sfc /scannow
позволяет проверить целостность системных файлов Windows. Если какие-то системные файлы отсутствуют или повреждены, утилита SFC попробует восстановить их оригинальные копии из хранилища системных компонентов Windows (каталог C:WindowsWinSxS).

Если команда sfc /scannow возвращает ошибку “
Программа защиты ресурсов Windows обнаружила повреждённые файлы, но не может восстановить некоторые из них / Windows Resource Protection found corrupt files but was unable to fix some of them
”, скорее всего утилита не смогла получить необходимые файла из хранилища компонентов (образа) Windows.

В этом случае вам нужно попробовать восстановить хранилище компонентов вашего образа Windows с помощью DISM.

После восстановления образа вы можете повторно использовать утилиту SFC для восстановления системных файлов.

Проверка целостности хранилища компонентов Windows с помощью DISM

Утилита DISM (Deployment Image Servicing and Management) доступна во всех версиях Windows, начиная с Vista.

Для сканирования образа Windows на наличие ошибок и их исправления используется параметр DISM /Cleanup-image. Команды DISM нужно запускать из командной строки, с правами администратора.

Чтобы проверить наличие признака повреждения хранилища компонентов в образе Windows (флаг CBS), выполните команду (не применимо к Windows 7/Server 2008R2):

DISM /Online /Cleanup-Image /CheckHealth

Эта команда не выполняет полное сканирование хранилища компонентов. Проверяются лишь записанные ранее маркеры повреждений и события в журнале Windows. Изменения в образ не вносятся. Команда проверит, не помечен ли ваш образ Windows как поврежденный и возможно ли исправить его.

В этом примере команда вернула, что с образом все хорошо:

No component store corruption detected.
The operation completed successfully.

Чтобы выполнить полное сканирование хранилища компонентов на наличие повреждений в хранилище компонентов Windows, запустите команду:

DISM /Online /Cleanup-Image /ScanHealth

Команда проверки образа Windows может выполняться довольно долго (от 10 до 30 минут). И вернет один из трех результатов:

• No component store corruption detected – DISM не обнаружил повреждения в хранилище компонентов;
• The component store is repairable – DISM обнаружил ошибки в хранилище компонентов и может исправить их;
• The component store is not repairable – DISM не может исправить хранилище компонентов Windows (попробуйте использовать более новую версию DISM или вам придется восстанавливать образ Windows из резервной копии, сбрасывать или полностью переустанавливать вашу копию Windows.

В Windows 7 и Windows Server 2008 R2 для использования параметра DISM /ScanHealth нужно установить отдельное обновление KB2966583. Иначе при запуске DISM будет появляться “
Ошибка 87. Параметр ScanHealth не распознан в этом контексте
”.

Команда DISM /ScanHealth может вернуть ошибки:

• Ошибка: 1726. Сбой при удалённом вызове процедуры;
• Ошибка: 1910. Не найден указанный источник экспорта объекта.

Это однозначно говорит о том, что ваш образ Windows поврежден и его нужно восстановить.

Восстановление образа Windows с помощью DISM /RestoreHealth

Чтобы исправить повреждения в хранилище компонентов образа Windows нужно использовать опцию RestoreHealth команды DISM. Эта опция позволит исправить найденные в образе ошибки, автоматически скачать и заменить файлы повреждённых или отсутствующих компонентов эталонными версиями файлов из центра обновлений Windows (на компьютере должен быть доступ в Интернет). Выполните команду:

DISM /Online /Cleanup-Image /RestoreHealth

В Windows 7/2008 R2 эта команда выглядит по другому:
DISM.exe /Online /Cleanup-Image /ScanHealth

Процесс сканирования и восстановления компонентов может быть довольно длительным (30 минут или более). DISM автоматически загрузит недостающие или поврежденные файлы образа с серверов Windows Update.

Восстановление выполнено успешно. Операция успешно завершена.

The restore operation completed successfully.

DISM /Source: восстановление образа Windows с установочного диска

Если на компьютере (сервере) отсутствует доступ в Интернет или отключена/повреждена служба Windows Update (как восстановить клиент Windows Update), то при восстановлении хранилища компонентов появятся ошибки:

• 0x800f0906 — Не удалось скачать исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра Источник (0x800f0906 — The source files could not be downloaded. Use the source option to specify the location of the files that are required to restore the feature);
• Ошибка: 0x800f0950 — Сбой DISM. Операция не выполнена (0x800f0950 — DISM failed. No operation was performed);
• Ошибка:0x800F081F. Не удалось найти исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра Источник (Error 0x800f081f, The source files could not be found. Use the «Source» option to specify the location of the files that are required to restore the feature).

<

Во всех этих случаях вы можете использовать альтернативные средства получения оригинальных файлов хранилища компонентов. Это может быть:

• Установочный диск/флешка/iso образ Windows
• Смонтированный файл wim
• Папка sourcesSxS с установочного диска
• Файл install.wim с установочным образом Windows

Вы можете указать WIM или ESD файл с оригинальным установочным образом Windows, который нужно использовать в качестве источника для восстановления файлов системы. Предположим, вы смонтировали установочный ISO образ Windows 11 в виртуальный привод D:.

Примечание. Для восстановления поврежденных файлов в хранилище компонентов из локального источника версия и редакция Windows в образе должна полностью совпадать с вашей.

С помощью следующей PowerShell команды проверьте, какая версия Windows установлена на вашем компьютере:

Get-ComputerInfo |select WindowsProductName,WindowsEditionId,WindowsVersion, OSDisplayVersion

Выведите список доступных версий Windows в установочном образе:

Get-WindowsImage -ImagePath "D:sourcesinstall.wim"

В нашем случае образ Windows 11 Pro в образе install.wim имеет
ImageIndex = 6
.

Для восстановления хранилища компонентов из локального WIM/ESD файла с блокированием доступа в интернет, выполните следующую команду (не забудьте указать ваш индекс версии Windows в файле):

DISM /online /cleanup-image /restorehealth /source:WIM:D:sourcesinstall.wim:6  /limitaccess

Или:
DISM /online /cleanup-image /restorehealth /source:ESD:D:sourcesinstall.esd:6  /limitaccess

Утилита DISM пишет подробный журнал сканирования и восстановления системных файлов в файл
C:WindowsLogsDISMdism.log
.

После восстановления хранилища компонентов вы можете запустить утилиту проверки системных файлов
sfc /scannow
. Скорее всего она успешно восстановит поврежденные файлы:

Программа защиты ресурсов Windows обнаружила поврежденные файлы и успешно их восстановила. 

Windows Resource Protection found corrupt files and successfully repaired them.

Если все системные файлы целы, появится сообщение:

Windows Resource Protection did not find any integrity violations

Восстановление образа Windows с помощью PowerShell

В версии PowerShell в Windows 10/11 и Windows Server 2022/2019 есть аналоги рассмотренных выше команд DISM. Для сканирования хранилища компонентов и поиска повреждений в образе выполните:

Repair-WindowsImage -Online –ScanHealth

Если ошибок в хранилище компонентов не обнаружено, появится сообщение:

ImageHealth State: Healthy

Для запуска восстановления системных компонентов и файлов наберите:


Repair-WindowsImage -Online -RestoreHealth


При отсутствии доступа к интернету эта команда может зависнуть в процессе восстановления образа. Вы можете восстановить системные компоненты из локальной копии образа Windows в виде WIM/ESD файла, скопированного с установочного ISO образа Windows 10 (здесь также нужно указать индекс версии Windows в wim файле в качестве источника восстановления):

Repair-WindowsImage -Online -RestoreHealth -Source D:sourcesinstall.wim:5 –LimitAccess

DISM: восстановление поврежденного хранилища компонентов, если Windows не загружается

Если Windows не загружается корректно, вы можете выполнить проверку и исправление системных файлов в оффлайн режиме.

1. Для этого загрузите компьютер с установочного образа Windows (проще всего создать загрузочную USB флешку с Windows 10/11 с помощью Media Creation Tool) и на экране начала установки нажмите
   Shift + F10
2. Чтобы разобраться с буквами дисков, назначенных в среде WinPE, выполните команду
   diskpart
   ->
   list vol
   (в моем примере диску, на котором установлена Windows присвоена буква C:, эту букву я буду использовать в следующих командах);
3. Проверим системные файлы и исправим поврежденные файлы командой:
   sfc /scannow /offbootdir=C: /offwindir=C:Windows
   
   
4. Для исправления хранилища компонентов используйте следующую команду (в качестве источника для восстановления компонентов мы используем WIM файл с установочным образом Windows 10, с которого мы загрузили компьютер):
   Dism /image:C: /Cleanup-Image /RestoreHealth /Source:WIM:D:sourcesinstall.wim:6
   
5. Если на целевом диске недостаточно места, то для извлечения временных файлов нам понадобится отдельный диск достаточного размера, например F:, на котором нужно создать пустой каталог:
   mkdir f:scratch
   и запустить восстановление хранилища компонентов командой:
   Dism /image:C: /Cleanup-Image /RestoreHealth /Source:D:sourcesinstall.wim /ScratchDir:F:scratch