DISM, unexpected behavior

There is no sooner or later. It is now, and for the last 3 months. The problem was never fixed. The overwrite install did not work ("Windows 10 installation has failed"), see above. The drive size is 32gb.

Hi,

The system partition on one of my W10 installs is only slightly bigger than your drive (33.66Gb to be precise) with over 19Gb free.
I never encountered any space problems so far. I do have hibernation disabled though.
With 2Gb of DRAM I assume you run the 32 bit version ?

Cheers,

No, it is 4 GB memory and 64 bit Windows 10.

I also have hibernate disabled, meaning the quick start, or rapid boot (or whatever it is called).

Hi,

Any reason why you're still on this older version of W10 ?
if not I'd start afresh with a clean install of Windows 1607, at least that version ran DISM just fine. The latest one (Creators) is troublesome on that aspect again.

Best,

fdegrove said:

...at least that version ran DISM just fine. The latest one (Creators) is troublesome on that aspect again.

Too true, there's already a lengthy threads on that - Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 implicated (again). However, boot from the install media to a command prompt and do an offline DISM RestoreHealth and it completes successfully. Thanks to DonCuthbert for spotting that one...
Use DISM to Repair Windows 10 Image

fdegrove: It is just the version that came installed, and then less than a month later, it has all these problems.

Bree/Kyhi: Are you saying that I should try to use DISM from, like, a DVD boot? If so, is it the same command that I have been trying to use?

ray5450 said:

Are you saying that I should try to use DISM from, like, a DVD boot? If so, is it the same command that I have been trying to use?

DonCuthbert described its use here...
Use DISM to Repair Windows 10 Image
...the next post being some comments from Brink, the one after that is mine showing a successful use of DISM. I booted from the same USB media I'd used to do the upgrade, then used this command:

dism /image:e:\ /cleanup-image /restorehealth /source:esd:d:\x86\sources\install.esd:1 /scratchdir:e:\scratch

Notes:

• this was for a 32-bit system, use ...\x64\sources\... if it's a 64-bit system.
• my system was Pro, for Home use ...\install.esd:2 (To find the correct index to use, run dism /get-imageinfo /imagefile:<full path to install.esd>
• The 'scratchdir' may be unnecessary - see Brink's comments.
• booting from the USB the drive letters will be different. Check your drive letters before you start, my 'C: drive' became E:

Hi,

But once online again DISM still doesn't work as it should and still reports errors it was suposed to have repaired whilst running it offline.

Makes no sense at all.

Cheers,

Hi,

ray5450 said:

fdegrove: It is just the version that came installed, and then less than a month later, it has all these problems.

No one seems to have any idea why you're stuck in a loop here as it should work.
You would like to upgrade to the AU Edition really, it's better than what you're running now and moreover it should resolve the problems you're experiencing.

Make an image backup (using MR Free preferably) before doing anything major and you'll be just fine.


Cheers,