Windows wont boot anymore - DISM doesnt work in Windows PE

FreeBooter · Oct 10, 2024

I understand is the I: drive letter belongs to install.wim USB flash drive and how did you create the bootable USB flash drive?

antspants · Oct 10, 2024

kelper said:
Your screenshots are too blurry to read.

Are you using your phone. They’re crisp and clean, just on a bit of an angle. Maybe he’s sloshed

WindowShadow · Oct 10, 2024

FreeBooter said:
Create yourself bootable Windows 11 USB flash drive using Media creation tool and boot your computer into WinRE using Windows 11 USB flash drive.

Create installation media for Windows - Microsoft Support

Learn how to create installation media for installing or reinstalling Windows.

support.microsoft.com

Hello,

i already have an USB with Ventoy where a 23H2 Windows 11 ISO is stored. I booted into it and executed the commands mentioned in the video. Should i re-download the ISO from Microsoft? I saw they only provide the 24H2 ISO.

My current Windows is 23H2

kelper · Oct 10, 2024

antspants said:
Are you using your phone. They’re crisp and clean, just on a bit of an angle. Maybe he’s sloshed

Yes, and I hadn't tapped on the preview image to open it. It's clear on phone now. My bad.

FreeBooter · Oct 10, 2024

WindowShadow said:
Hello,

i already have an USB with Ventoy where a 23H2 Windows 11 ISO is stored. I booted into it and executed the commands mentioned in the video. Should i re-download the ISO from Microsoft? I saw they only provide the 24H2 ISO.

My current Windows is 23H2

No Ventoy you use ISO file of Windows 11 you should create yourself one with Media Creation Tool.

WindowShadow · Oct 10, 2024

FreeBooter said:
No Ventoy you use ISO file of Windows 11 you should create yourself one with Media Creation Tool.

Hello,

okay. Im going to see that i get a second usb where i burn the image on the USB drive. I keep you update once im back at my pc.

kelper · Oct 10, 2024

If you have a Windows iso on the Ventoy, you can click or double-click on it to mount. Then run setup exe. It will offer a repair option.

Perhaps FreeBooter is not familiar with Ventoy?

WindowShadow · Oct 10, 2024

FreeBooter said:
No Ventoy you use ISO file of Windows 11 you should create yourself one with Media Creation Tool.

Hello,

here is an quick update:
I downloaded the MediaCreationTool and ran it on a USB drive. I booted of it and launched a cmd shell.
I first had to change the drive letters from my drives to the right one. My C drive was labeled as F. So i opened diskpart and changed all of that. I attached the logs so you can see what i did.

Next up i executed the DISM command. See my attached logs. Still returned the same error...

diskpart_logs.txt -> diskpart commands i executed
dism_console.txt -> dism commands i executed
dism.log -> the particular log file from DISM on X:\

And the install.esd file is stored now on G:\

Thanks

FreeBooter · Oct 10, 2024

[C:\] is not recognized by the DISM FFU provider

I have no clue why you had to change drive letter assignment are you dual booting even so you can place any drive letter after /image switch.

Execute below command:

Code:

DISM /Image:C:\ /Cleanup-Image /?

WindowShadow · Oct 10, 2024

FreeBooter said:
I have no clue why you had to change drive letter assignment are you dual booting even so you can place any drive letter after /image switch.

Execute below command:

Code:

DISM /Image:C:\ /Cleanup-Image /?

Hello,

this could be because sometimes i connect my SATA SSD to my pc and boot into on another windows 11 instance. On this SSD i have Windows 11 24h2 running where i sometimes boot into to test programs. its an external ssd.

For the command i executed it. It outputs the parameters and additional context. I attached it.

Thanks

FreeBooter · Oct 10, 2024

The command i asked you to execute works you don't need to change drive assignment, instead of using C: drive letter you can use any drive letter assigned to Windows 11 installed partition.

WindowShadow · Oct 11, 2024

FreeBooter said:
The command i asked you to execute works you don't need to change drive assignment, instead of using C: drive letter you can use any drive letter assigned to Windows 11 installed partition.

Hello,

i appreciate your patience and help.

I executed the command without changing the drive letter. It actually now is doing something. But it stops or rather skips to 100% when reaching approximately 60%.

Batch:

DISM  /Image:F:\ /Cleanup-Image /RestoreHealth /Source:esd:G:\sources\install.esd:5 /LimitAccess

I looked online about it and found only the problem being related to not defining its a ESD or WIM. So i executed this command:

Batch:

DISM  /Image:F:\ /Cleanup-Image /RestoreHealth /Source:esd:G:\sources\install.esd:5 /LimitAccess

But Unfortunately it stops again with the same error.

(i translated it for everyone here)
Error: 0x800f081f
The source files could not be found.

It also complains about the /ScratchDir Parameter. I tried to add it to my Windows Drive: F:\scratchdir.

DISM /Image:F:\ /Cleanup-Image /RestoreHealth /ScratchDir:F:\scratchdir /Source:esd:G:\sources\install.esd:5 /LimitAccess

But this fails too. I added the logs

dism.log -> executed without scratch dir
dism_with_scratchdir.log -> executed with scratch dir

Thanks

FreeBooter · Oct 11, 2024

[F:\] is not recognized by the DISM FFU provider.

The provider WimManager does not support CreateDismImage on F:\

I don't know why Dism not working for you, maybe mounting the install.esd or install.wim file and to extract and replace the device driver causing the bsod or even rename it with .old extension and try booting again.

SIW2 · Oct 11, 2024

WindowShadow said:
Hello,

Thanks for the suggestion.
I didn’t try C:\offline yet. I only applied C:\. Will try this and keep you updated.

The \offline example is confusing. The only reason to do that that is if the image is mounted in a folder called c:\offline

If trying to service an installed image on the root of a partition the command is just the driveletter:\

The source files could not be found.

If it starts and then stops with that message it could mean the exact version of some file it wants to replace is not in the source. In other words you need a source that contains the same file versions as the image you are trying to repair.

according to ms

When specifying a source:

Only use RTM media regardless of whether the source is a WIM or a mounted Windows image. Refresh media has older file versions excluded from the media and the target operating system may need these files.

Make sure the source is patched to the latest Cumulative Update. If the target OS is patched to a higher level than the source, adding features or repairing Operating Systems may fail because the target OS needs updated files that are not present in the source.

If you still have your restore point , then there must be a shadow copy . I have done this several times and it worked every time. Maybe I was lucky the linked files were not damaged . It is worth a try :

create a wim image of the shadow copy and then you can apply the wim image to the windows partition.

Before applying the wim, I suggest creating a folder on the windows partition called something like OLDOS, then move evrything on the partition (not the documents and settings link ) into the OLDOS folder. So everything is in there just in case. Or you could just format the windows partition before applying the wim but then you won't have all the previous stuff saved.

[ Alternatively the wim image can be applied to different partition, but you will need to add a bcd entry and adjust the osletter alias before booting into it. Not as complicated as it sounds ( I have done it often) but I cba to explain all that. ]

SIW2 · Oct 11, 2024

this shows how to capture a shadowcopy into a .wim file

Anyway to fix Windows 11 repair loop on another internal Windows Driv? - Windows 10 Help Forums

Hi, I tried all the command promps in the CMD but nothing worked. I have 2 internal SSDs, windows 11 and windows 10. I can still boot my Windows 10 and see my Windows 11 drive, is there anything I can do manually through the files? specs: windows 11 cpu:

www.tenforums.com

If you are really stuck , you can borrow one of my fancy pe which has everything needed and is easy to see what you are doing.

The namespace folders that should be moved into OLDOS folder before applying the wim are:

SIW2 · Oct 11, 2024

4169-usb.iso

it should be extracted to usb stick using something like this

SIW2 · Oct 11, 2024

After booting from the usb it gets to a desktop like this

WindowShadow · Oct 11, 2024

SIW2 said:
If it starts and then stops with that message it could mean the exact version of some file it wants to replace is not in the source. In other words you need a source that contains the same file versions as the image you are trying to repair.

according to ms

I read something similar that DISM is complaining that it cant find the right package version inside the ISO file. I found this (NRoach44 Blog) article about it where he goes through the CBS.log file and adds the appropriate package for the version. Could be also an issue that i had a 24H2 Windows PE running.
I might have to try to burn the 23H2 Build Number 22621 ISO (from uupdump) on a usb and try to see if DISM finds the right version and the right package again. If not look through the CBS.log and add the packages.

SIW2 said:
Before applying the wim, I suggest creating a folder on the windows partition called something like OLDOS, then move evrything on the partition (not the documents and settings link ) into the OLDOS folder.

Does applying the WIM image on the windows drive overwrite the OLDOS Folder if its in the root folder of the drive? (e.g. F:\OLDOS\) Or should i just move everything to a different drive? Also please explain what you mean by "not the documents and settings link". Do you mean the Documents folder inside the Users folder?

SIW2 said:
The namespace folders that should be moved into OLDOS folder before applying the wim are:

Correct me if am wrong:
I capture a WIM image from my restore point/shadow copy with the article from tenforums, copy the folders selected in the picture to and folder called F:\OLDOS\... or Z:\OLDOS\... and then apply the shadow copy image on the Windows Partition?

Im currently not at my PC but ill be home again in 1-2 hours and then i try these steps provided with the PE image you provided (thanks for the image).

Edit:

Forgot to ask. Should i apply the image from the Windows PE Enviroment you provided or an Windows Build with the same Build Number i had?

SIW2 · Oct 11, 2024

Does applying the WIM image on the windows drive overwrite the OLDOS Folder if its in the root folder of the drive? (e.g. F:\OLDOS\)

No. That is why I suggest after capturing the wim, create some entirely new folder e.g. named oldos and moving everything into it ( except the documents and settings link, leave that where it is )

anything on the root that has the original pathnames will be overwritten by the same pathnames in the wim when it is applied.

Because the wim does not contain a folder called oldos , it will be untouched.

More advanced users can get away with just moving the windows namespace folders into oldos because they would know how to exclude other files/folders from being captured into the wim file using wimscript.ini

for example if there is giant folder on the root called mycatpictures it can be excluded using a wimscript.ini . Then it wont be in the wim and wont be overwritten when applying that wim.

It will also keep the size of the wim down.

I do it all the time. My wimscript.ini excludes a lot of stuff

I prefer to use wimlib-imagex for capturing, it is quicker

using wimlb

wimlib-imagex capture \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\ "o:\shadow.wim" --compress=fast --config=path_to_wimscript.ini

using dism

Code:

Dism /Capture-Image /ImageFile:"O:\shadow.wim" /CaptureDir:\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\ /Name:Somenameyoulike /ConfigFile:path_to_WimScript.ini

SIW2 · Oct 11, 2024

a simple wimscript.ini

Code:

[ExclusionList]
\$ntfs.log
\hiberfil.sys
\pagefile.sys
\swapfile.sys
\System Volume Information
\RECYCLER
\Windows\CSC
\mycatpictures
\some other stuff you dont want included

[CompressionExclusionList]
*.mp3
*.zip
*.cab
\WINDOWS\inf\*.pnf

Windows wont boot anymore - DISM doesnt work in Windows PE

Well-known member

My Computer

Like a rolling drone.

My Computers

New member

My Computer

Well-known member

My Computers

Well-known member

My Computer

New member

My Computer

Well-known member

My Computers

New member

Attachments

My Computer

Well-known member

My Computer

New member

Attachments

My Computer

Well-known member

My Computer

New member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

Attachments

My Computers

Well-known member

My Computers

New member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Similar threads