Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

In fact, it also shows on 90% of all apps on Processes tab - apps that are actively running lol.

johngalt said:

In fact, it also shows on 90% of all apps on Processes tab - apps that are actively running lol.

Sorry, just saw, I'm in wrong thread... but: 0 suspended means "not suspended". 1 suspended would read "it is suspended"

It shows 1 Suspended. I have that in front of Cortana

(And a few others)

johngalt said:

It shows 1 Suspended. I have that in front of Cortana

I have very few suspended: (and Cortana should be suspended

AndreTen said:

Sorry, just saw, I'm in wrong thread... but: 0 suspended means "not suspended". 1 suspended would read "it is suspended"

0 Suspended is not binary number here, it just means that none are suspended, 1 suspended would mean that one instance (thread) is suspended but when I look at mine that none are really suspended although some are. In Startup tab, when I open it first time, for a split second shows old way, Enabled or Disabled.

CountMike said:

0 Suspended is not binary number here, it just means that none are suspended, 1 suspended would mean that one instance (thread) is suspended but when I look at mine that none are really suspended although some are. In Startup tab, when I open it first time, for a split second shows old way, Enabled or Disabled.

Good point. Wasn't aware of that. Edge has 5 suspended. And hasn't been run since yesterday..

I was wrong, I have few suspended processes but in startup it's still wrong.

I once again tried to upgrade my Skip Ahead build 17083 to 17604 by first disabling the hiberfile completely, but no luck there. I still get SYSTEM_THREAD_EXCEPTION_NOT_HANDLED during first reboot phase.

Seems the issue is something common, not fast startup related, in builds 17093, 17101 and 17604, since none of those install (with nor without hiberfile enabled), but 17107 installs without issues.

slicendice said:

I once again tried to upgrade my Skip Ahead build 17083 to 17604 by first disabling the hiberfile completely, but no luck there. I still get SYSTEM_THREAD_EXCEPTION_NOT_HANDLED during first reboot phase.

Seems the issue is something common, not fast startup related, in builds 17093, 17101 and 17604, since none of those install (with nor without hiberfile enabled), but 17107 installs without issues.

Wonder if this had something to do with your issues?

Microsoft releases new Windows 10 preview with more proactive Windows Update | VentureBeat

johngalt said:

Wonder if this had something to do with your issues?

Microsoft releases new Windows 10 preview with more proactive Windows Update | VentureBeat

It could be but I doubt it is directly related to this issue in particular. One never knows though. MS is always so secretive when it comes to what they changed/fixed/broken. They only tell us all the irrelevant information and leave out all the relevant core and system related information.

It is absolutely impossible to find the root cause and possible workarounds for issues on builds where NO debug symbols are released (which is the case for most builds).

A record of "We changed default font size from 12px to 14px in settings app" is pretty much irrelevant information or is very obvious if one opens up the Settings up. But information like "We re-enabled a kernel feature that enables us to open ELF binaries natively" is very relevant, since it is not obvious and such drastic changes can cause a lot of misbehavior because of all the newly enabled code loops.