Windows 10 October 2018 Update rollout now paused

kado897 · 17 Oct 2018

slicendice said:

Could someone please make me a favor?

Open up Task Manager, then order tasks by CPU-usage. Finally right-click on desktop to get the context-menu and then hover mouse over NEW.

I get 55-65% CPU usage in total from Explore and Service Host: State Repository Service on 2 computers. Also on one of the computers the NEW-context menu opens up really slowly.

Does anybody else experience this issue?

I'm on 17763.104

on 17763.104 in a VM I get a spike to 55% in Explorer and appmodel(State Repository Services) which only lasts a few seconds.

LEOPEVA64 · 17 Oct 2018

slicendice said:

Also on one of the computers the NEW-context menu opens up really slowly.
Does anybody else experience this issue?
I'm on 17763.104

That bug is quite old, there are reports of that from build 17682, I mentioned it on Twitter and also on Reddit some time ago. I remember that here in Ten forums someone also mentioned it a long time ago but I have not found that comment yet.

Bree · 17 Oct 2018

jimbo45 said:

Hi folks
on 1809 if you use things like Wintogousb it will fail due to NTFS file compression...
...Ms obviously did change something in the file system...

Not sure if it's related, but of the four machines I updated from 1803 to 1809 on one of them the upgrade switched it to using a compact OS. Use the command compact /compactos:query in a command prompt (admin) to see if that's the case.

Compress or Uncompress Windows 10 with Compact OS | Tutorials

kado897 · 17 Oct 2018

Bree said:

Not sure if it's related, but of the four machines I updated from 1803 to 1809 on one of them the upgrade switched it to using a compact OS. Use the command compact /compactos:query in a command prompt (admin) to see if that's the case.

Not mine. I wonder what informs the decision.

Windows 10 October 2018 Update rollout now paused-image-001.png

Bree · 17 Oct 2018

kado897 said:

Not mine. I wonder what informs the decision.

In my case the one machine for which 1809 decided to use a compact OS was the highest spec machine of the four, having an I7 processor and more RAM than any of the others. It certainly wasn't on ground of disk space, as it had 129GB free at the time.

Wiley Coyote · 17 Oct 2018

So, I'm in the "compact" mode now:

Windows 10 October 2018 Update rollout now paused-compact.png

Is this something I need to concern myself over? Or continue on in blissful ignorance?

Bree · 17 Oct 2018

Wiley Coyote said:

So, I'm in the "compact" mode now:
Is this something I need to concern myself over? Or continue on in blissful ignorance?

I noticed no obvious effects from running a compact OS. I have since re-imaged that machine back to 1803, but that was down to an (apparently) unrelated problem with networking when using a Hyper-V network switch. The host machine had problems writing to (but not reading from) shares on other physical machines on the network, but no problem with shares on VMs.

Back in 1803 that machine says:

The system is not in the Compact state but may become compact as needed.

While the machines that didn't become compact all say:

The system is not in the Compact state because Windows has determined that, it is not beneficial for this system.

slicendice · 17 Oct 2018

Thanks guys for testing the context menu CPU usage spike issue for me. So it seems I'm not alone with this one.

Wonder what on earth Windows is trying to do during that short spike. Makes no sense, but then again nothing much else makes any sense on current state of Windows. It does a lot of weird stuff behind the scenes.

This is the most odd Windows 10 release ever.

kado897 · 17 Oct 2018

Wiley Coyote said:

So, I'm in the "compact" mode now:

Is this something I need to concern myself over? Or continue on in blissful ignorance?

My understanding is that it is done to save disk space at the expense of performance as I said earlier I wish I knew what informed the decision.

Edit: We have a tutorial. Compress or Uncompress Windows 10 with Compact OS

Bree · 17 Oct 2018

kado897 said:

My understanding is that it is done to save disk space at the expense of performance as I said earlier I wish I knew what informed the decision.

Edit: We have a tutorial. Compress or Uncompress Windows 10 with Compact OS

From the blog referenced by that tutorial...

One important factor is the amount of memory (RAM) a device has. The amount of RAM a device has determines how often it retrieves system files from storage. Another important factor is how quickly a device’s CPUs can run the decompression algorithm when retrieving system files. By considering these and other important factors, Windows is able to assess if a device can use compression without reducing human-perceivable responsiveness.

As I said, my machine that got compacted by the 1809 update had the fastest cpu and more RAM than the others, 8GB as opposed to 4GB.