Windows 10: DISM fails with error 112 when NTFS compression is enabled WinPE 10

In today’s post, we will attempt to resolve the issue of NTFS compression in WinPE 10 using all available disk space on your Windows computer. […]

This post DISM fails with error 112 when NTFS compression is enabled WinPE 10 is from TheWindowsClub.com.

read more...

 

NTFS Compression on Event Logs

Anyone ever try doing NTFS compression on their Error Logs?
It's all text, so it should compress pretty well.






Anyone else try this? I suppose it's only useful in server-land when you have huge event logs..

To compress:
Run services.msc
Find Event Log and set to "Disabled"
Reboot
Go to c:\windows\system32\config
NTFS Compress anything that ends in .evt
Run services.msc
Find Event Log and set to "Automatic"
Reboot

 

NTFS compression

I bought ASUS E200H: Win 10 Home; 32GB of SSD (the operating system occupies around 20GB, so only around 10GB is left for me).

After installing all the programs that I need, I had around 1GB of free space.

I was advised to perform the NTFS compression on the whole C:.

So I checked the NTFS compression fir C:, and it started to run.

As it ran, I noticed that the Windows Manager says that there is less and less free space.

When it was around 200MB, i decided to stop the process, and unchecked the compression.

The process started running again, and the free space continued decreasing, and soon reached 0 bytes.

So the question is, what should I do now?..

Should I let the compression run to the end? Or keep it decompressed - but in this case how can I regain the free space that I had before running int this procedure?.. Or possibly compress only some folders - which yes and which no?..

Thanks in advance.

 

Add packages to WinPE version 10.0.15063.0

I am unable to add any packages to my WinPE wim file using DISM.

I consistently get the following error:

Error: 0x800f081e

The specified package is not applicable to this image

Does anyone have any suggestions or workarounds?