New
#11
properties
Have you changed the default option here, according to your screenshot drive should be H.
Roy
Have you changed the default option here, according to your screenshot drive should be H.
Roy
Thank you Roy, for taking time helping out with my problem!
Yes, I have tried changing attributes for drive H, in addition to the single file on the drive.
Compression for H can be set ON/OFF without getting Windows error message.
(Tried both options: Only H, and H incl. folders/ files)
However, the box is always unchecked when I go back to see properties status.
Properties for the .flkb file on drive H remains stuck with a checked box, I get a Windows error message when trying to disable.
The paradox is that Windows never started the compression process in the first place, it only marked the file as if!
Last edited by mp5; 22 Nov 2015 at 09:13.
What settings here,
Roy
I have this squirrelled away, maybe it will help:
Compression is sometimes turned on by disk cleanup, to prevent this from happening again delete this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Explorer\VolumeCaches\Compress old files
You can export the key before deleting it, just in case you want it back. Disable compression from disk properties or use the following command:
compact /u /a /f /i /s:c:\
Change c:\ to the letter assigned to the drive you are working with.
I'm surly no expert but is it possible that their isn't enough room on the drive to decompress it?
The picture only shows 2.1MB free space.
- I was me that unfortunately tried to turn on compression! This is explained in my first post!
But Windows aborted immediately with an error message; Not enough space!
So main issue is Windows marked the file's properties with "compression ON" and now refuses to turn it off for the same reason; Not enough space!
- I don't have that registry key! Don't know how or why it disappeared..
- I ran your suggested command. It does not say OK for the Locker -file yet, but I guess the blinking cursor means it's working on it?
It's been running for a two hours now.. Since the Locker -file is not really compressed physically, I would've thought it go rather quick!?
Last edited by mp5; 24 Nov 2015 at 18:56.
It is NOT enough space for decompression, but thing is nothing has ever been compressed!
Please read my first post! :)
Thanks...
Last edited by mp5; 24 Nov 2015 at 19:31.
There is an 'Uncompress' method of the CIM_Directory WMI object. It's worth a shot...
Enter these lines in a PowerShell shell.
Code:$folder = (gwmi -q "SELECT * FROM CIM_Directory Where Name='C:\\folder\\to\\uncompress'") $folder.Uncompress()