Win10 keeps compressing C drive files (new and old). Cannot stop it.

Dear Tenforums users,

I have recently (I think it started less than a week ago) encountered problems or rather peculiarities with my Lenovo laptop:
two blue arrows started appearing on nearly all my files and folders (image files, Word documents e.g.). In addition, whenever I create a new file or folder, the same happens right away. Could a recent update be responsible for this and has anyone else encoutered this? I have found a similar phenomenon in this thread, but alas, no solution: https://answers.microsoft.com/en-us/...2-0f49f7696d6b

The major problems that I have encountered are:
1. I am unable to, for example, copy image files from one folder to the next.
2. CHKDSK /r or /f does not work, neither does sfc /scannow or updating Windows work.
3. I have a feeling that this "auto-compressing" is filling up the remaining space (+-10 gig)
4. whenever I try to "decompress" files by unchecking the "compress contents to save disk space" option, it keeps hanging.
5. The huge JPG files are not readable - I get the message that this filetype is not supported

Screenshots of the arrows on newly created files/folders: (nearly all files on C drive are like this now)


Screenshot of the huge JPG files: (as you may appreciate, these are ridiculous file sizes for JPG files...)


I do not know how to proceed from here. I hope that you can aid me in this matter.

Yours,

esmorax

Ztruker said:

A change (1803????) to Windows 10 turns on compression on some computers without you asking for it or knowing about it. There was a discussion about it recently but I can't find it now.
@Kari, do you know where that discussion was?

Edit: Found it. Starts about here and goes on for quite awhile: Windows 10 October 2018 Update rollout now paused

Hi Ztruker!

First of all, thank you for the link! (and the others for their interest)

I have used the command compact /compactos:query and the response was:
"C:\WINDOWS\system32> compact /compactos:queryThe system is in the Compact state. It will remain in this state unless an administrator changes it."

Would decompressing my C drive be able to fix all of the above problems? Or will I need to rollback the update/wait for MS to rollout a decent fix?

In either case, I think that I will attempt the decompressing tomorrow and let you know!

Esmorax

Ztruker said:

Yes, uncompress the drive then turn off Compactos will get rid of it permanently.

When I query it on my system, I get:

Code:

>compact /compactos:query
The system is not in the Compact state because Windows has determined that, it
is not beneficial for this system.

Okay! I will give it a shot and report back later!

Esmorax

Ztruker said:

A change (1803????) to Windows 10 turns on compression on some computers without you asking for it or knowing about it. There was a discussion about it recently but I can't find it now.

Edit: Found it. Starts about here and goes on for quite awhile: Windows 10 October 2018 Update rollout now paused

Starts with my post, I see

Yes, on one machine that I upgraded to 1809 the upgrade did turn on compactos. But I think I should point out that it was JUST the OS that was compacted. None of the other folders were compressed as is the case for the OP, just the OS.

It may even have been a sensible thing to do. Setup may have ".... determined that it is beneficial for this system". That would be expected for a tablet with a 32/64GB SSD. I was just surprised to see it with 150+ GB still free on the HDD. Probably the MS algorithm found that time saved by reading less data was more than the time taken to uncompress it on the fly, but MS don't document how this is determined.