New
#21
Yes, it's the easy way! Just 5 $ And some years ago I lived in Bremen
Yes, it's the easy way! Just 5 $ And some years ago I lived in Bremen
So NW connect &
Wpeutil InitializeNetwork
Wpeutil DisableFirewall
mkdir D:\scratch
Dism /image:\ /Cleanup-Image /RestoreHealth /ScratchDir:\scratch
My mother (96) has a family tree that goes back to the 1700s. My grandmother & grandfather fled Germany to escape WWI. I still have countless relatives there. I'll PM you her maiden name.
I'm going to have to go get set up in another room - just let me know that's what you want me to do.
You can download "Explorer++" it's portable and copy it to your USB-Stick in the WIN-DIR. That makes it much easier afterwords.
Explorer++ - Download
Well unfortunately DISM did not work. Got 0x80029c4a. I know I had network connectivity, did an IPConfig and did have an IP address. I've attached the DISM log - 11K.
I had to disconnect one of my access points to get a long enough.
I used what you gave me the other night:
Wpeutil InitializeNetwork
Wpeutil DisableFirewall
mkdir D:\scratch
Dism /image:D:\ /Cleanup-Image /RestoreHealth /ScratchDir:D:\scratch
Reading about DISM it looks like /Image is the path to the root directory of an offline Windows image.
So would we not use Dism /image:G:\<something> ? I would think the something would be where on the windows 10 CD the O/S is or maybe just the root of the windows 10 CD.
Anyway, it's like 8pm where you're at & I have to get. If you want me to try Dism /image:G:\ /windir:D:\windows /SysDriveDir:D:\ /Cleanup-Image /RestoreHealth /ScratchDir:D:\scratch
G: is my DVD drive. I'm not certain we need /SysDriveDir:D:\ SysDriveDir: Specifies the path to the system-loader file named BootMgr. Is it D: or is it H: (the EFI volume)
Last edited by Antique; 4 Weeks Ago at 13:03.
You are shooting at sun without knowing the cause of the boot problem, let us have Startup Repair log file, maybe it will let us know what is the boot problem.
Did you run from Recovery Environment? If yes, try the USB and in command prompt type
X:> diskpart
list vol
exit
to verfy that the Letter is still (D:) It might have changed.
You also can use Explorer++
Then in cmd you just type: explorer++ and you can check the right drive letter and change accordingly in the command:
Dism /image:D:\ /cleanup-image /restorehealth /scratchdir:d:\scratch
Your WinRE.wim might be too old
If Windows 10 or Windows 11 has missing or corrupted system files, in this video, i will guide you how to repair the corrupted system files using the DISM and SFC command tools from Windows Recovery Environment.
@FreeBooter
There is no boot problem
D: is definitely the windows drive. I'm using a DVD to move stuff back & forth using the diskpart to mount it, I do a list volume every time. D is the windows drive.
I used what you gave me the other night
Wpeutil InitializeNetwork
Wpeutil DisableFirewall
mkdir D:\scratch
Dism /image:D:\ /Cleanup-Image /RestoreHealth /ScratchDir:D:\scratch
Reading about DISM it looks like /Image is the path to the root directory of an offline Windows image.
So would we not use Dism /image:G:\<something> ? I would think the something would be where on the windows 10 CD the O/S is or maybe just the root of the windows 10 CD.
Would Dism /image:G:\ /windir:D:\windows /SysDriveDir:D:\ /Cleanup-Image /RestoreHealth /ScratchDir:D:\scratch
G: is my DVD drive. I'm not certain we need /SysDriveDir:D:\ SysDriveDir: Specifies the path to the system-loader file named BootMgr. Is it D: or is it H: (the EFI volume)