Solved Dism.exe issue!!

zbook said:

When available please update the progress with the steps in post #20.

Click to expand...

Shall do for you, since am not a Windows/computers literate have a few questions:

1. Should I create a restore point even before starting?
2. Would it benefit my laptop's Windows 11, like lab works to check for any disease improvements?
3. Hope it would be of some research for you too, would gladly do it.

The only thing that bothers me is not to mess up the OS, since don't have the time and energy to perform a clean install at this time.

Shall keep you posted, and if I find something confusing would ask.

Best regards!

zbook said:

1) Please run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Open administrative command prompt and copy and paste:

DISM /Online /Get-OSUninstallWindow

Post a share link



3) Create a new restore point:

Create System Restore Point in Windows 11

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

Click to expand...

Step #1 done:

Microsoft Windows 11 Pro Version 24H2 (OS Build 26100.2605)

==================================================================

Started on Fri 12/20/2024 at 7:57:28.90

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Fri 12/20/2024 at 7:58:42.81

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.2605

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on Fri 12/20/2024 at 7:59:36.32

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.2605

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Fri 12/20/2024 at 8:00:13.45

[ChkDsk /Scan]

The type of the file system is NTFS.
Volume label is W11.

Stage 1: Examining basic file system structure ...
960768 file records processed.
File verification completed.
Phase duration (File record verification): 3.26 seconds.
14060 large file records processed.
Phase duration (Orphan file record recovery): 4.54 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.02 milliseconds.

Stage 2: Examining file name linkage ...
614 reparse records processed.
1064622 index entries processed.
Index verification completed.
Phase duration (Index verification): 5.30 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 338.74 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.68 milliseconds.
614 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.59 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 143.75 milliseconds.
51928 data files processed.
Phase duration (Data attribute verification): 0.03 milliseconds.
CHKDSK is verifying Usn Journal...
40835520 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 81.16 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

498996223 KB total disk space.
63371468 KB in 182507 files.
142808 KB in 51929 indexes.
0 KB in bad sectors.
1097119 KB in use by the system.
65536 KB occupied by the log file.
434384828 KB available on disk.

4096 bytes in each allocation unit.
124749055 total allocation units on disk.
108596207 allocation units available on disk.
Total duration: 9.15 seconds (9153 ms).

==================================================================

Started on Fri 12/20/2024 at 8:00:30.31

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\DELL-BMT2012\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

7

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\DELL-BMT2012\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=2911
CurrentUsage=32
Description=C:\pagefile.sys
InstallDate=20221208185028.723662+300
Name=C:\pagefile.sys
PeakUsage=33
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

FALSE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\DELL-BMT2012\ROOT\CIMV2:Win32_ComputerSystem.Name="DELL-BMT2012"'
Property(s) update successful.
==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}
isolatedcontext Yes

==================================================================

Finished on Fri 12/20/2024 at 8:00:32.78
It took 3 minutes and 4 seconds to complete the operations.


Step #2:

Microsoft Windows [Version 10.0.26100.2605]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>DISM /Online /Get-OSUninstallWindow

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.2605


Error: 1168

Element not found.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Windows\System32>

The results were good.

Please make a new restore point.

zbook said:

The results were good.

Please make a new restore point.

Click to expand...

Thanks for the expert comments.
After the restore point, than what do I do? Apologizes for my ignorance.

That may complete the thread?



Consider making free or pay backup images.

(Acronis, Aoemi, EaseUS, Hasleo, Macrium, Paragon, etc.)

You should always have up to date backups of your system. Even with system backups I recommend making backups of your patients' files.

Alexey2912 said:

Hi,

After sfc scan it still stalls at 70%.....any ideas or fixes?

Thanks.


Dism.exe /online /Cleanup-Image /StartComponentCleanup

Click to expand...

Hi,

First of all, run dism /online /get-packages /format:table >packages.txt
At the "Package Identity" column, find out the Package Name of the update that you want to remove. *

There is problem with package "Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10", after remove this package , dism will working correctly.

Now, run dism /Online /Remove-Package /PackageNameackage_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

After remove package , You can run Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore, the problem wiil left, no reclaim package and at the end run DISM /Online /Cleanup-Image /ScanHealth, to verify status image

Jofe