From Newsgroup: alt.comp.os.windows-11

Not even a domain-wide Group Policy explicitly allowing optional updates works to fix this. So I guess I'm stuck with a non-resizable Start Menu on 26H2.

Fuck you too, Pajeet.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Thu, 10/8/2026 2:54 AM, Anonymous wrote:

Not even a domain-wide Group Policy explicitly allowing optional updates works
to fix this. So I guess I'm stuck with a non-resizable Start Menu on 26H2.

Fuck you too, Pajeet.

For anyone who has not clicked the Enablement Upgrade to 26H2 from 25H2,
stay away from that Start setting. I had to do a Repair Install here
a couple hours ago, due to the OS shutting down in under a minute after
a reboot. I was able to use another profile to get into Windows 11 and
do a Repair Install and now am back on my regular Profile OK. Whereas
I've had these "+5VSB power-off" events before, in this case it
had become reproducible, and every time after a reboot, the +5VSB
would drop and there would be no graphics and no keyboard input possible.
Since these leave no entry in Event Viewer, I cannot debug these.

This is unlikely to happen to any of you out there, but having two incidents related to the Start setting so close together, is unnerving.

Paul
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

Paul wrote:

For anyone who has not clicked the Enablement Upgrade to 26H2 from 25H2,
stay away from that Start setting.

Which one? this from the other "start" thread

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StartMenu
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Fri, 10/9/2026 4:20 AM, Andy Burns wrote:

Paul wrote:

For anyone who has not clicked the Enablement Upgrade to 26H2 from 25H2,
stay away from that Start setting.

Which one? this from the other "start" thread

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StartMenu

I would recommend not modifying Settings : Personalize : Start,
from Auto to Big or Small. It likely modifies something
in that Registry area, and maybe in doing so, damages something.
I don't know, I'm just guessing at this point, as I don't
have any other things I've changed lately.

After the Repair Install, I'm more or less back to where I was
in terms of install state (26200.9457), and the OS is now staying up, instead of dropping dead after 60 seconds or so (reproducible). I could use
a second profile to log into the broken OS, and then the broken OS would stay up.
It was my regular profile that caused the OS to drop dead. When the OS
drops dead, it doesn't leave a crash log of any sort to work with.

Paul
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

Paul wrote:

I would recommend not modifying Settings : Personalize : Start,
from Auto to Big or Small. It likely modifies something
in that Registry area, and maybe in doing so, damages something.
I don't know, I'm just guessing at this point, as I don't
have any other things I've changed lately.

Setting it to Large was the first thing I did after updating to 26H2 8-O
So far no bad effect, I'll leave it alone but thanks for the heads up.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 09-Oct-26 4:39 AM, Paul wrote:

I would recommend not modifying Settings : Personalize : Start,
from Auto to Big or Small. It likely modifies something
in that Registry area, and maybe in doing so, damages something.
I don't know, I'm just guessing at this point, as I don't
have any other things I've changed lately.

No impact on 26H2 W11 Pro on this device when changing setting from Auto
to Small or Large(i.e. your 'Big' term).

Also note, Auto on this device configures the same as Small.
i.e. Auto or Small - exact same condition

Win11 Pro version build
- after 26H2 Enablement is 26300.9550
- before 26H2, 25H2 was 26200.9550

Fyi:
Build 9550 included SSU 22621.9539
Build 9457 included SSU 22621.9441
Build 9445 included SSU 22621.9441

No ideas on the cause of your issue.
- Maybe a glitch related to enabling from 26200.9457 to 26H2
23200.9550 or but unlikely, the SSU.??
--
...w¡ñ§±¤ñ
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Sat, 10/10/2026 5:38 PM, ...w¡ñ§±¤ñ wrote:

On 09-Oct-26 4:39 AM, Paul wrote:

I would recommend not modifying Settings : Personalize : Start,
from Auto to Big or Small. It likely modifies something
in that Registry area, and maybe in doing so, damages something.
I don't know, I'm just guessing at this point, as I don't
have any other things I've changed lately.

No impact on 26H2 W11 Pro on this device when changing setting from Auto to Small or Large(i.e. your 'Big' term).

Also note, Auto on this device configures the same as Small.
 i.e. Auto or Small - exact same condition

Win11 Pro version build
 - after 26H2 Enablement is 26300.9550
 - before 26H2, 25H2 was 26200.9550

Fyi:
Build 9550 included SSU 22621.9539
Build 9457 included SSU 22621.9441
Build 9445 included SSU 22621.9441

No ideas on the cause of your issue.
 - Maybe a glitch related to enabling from 26200.9457 to 26H2 23200.9550 or but unlikely, the SSU.??

It's something specific to this machine.

I have two of these motherboards, the other one doesn't do this.

This one also has weird UEFI behavior, more weird than the
other machine can produce. Both machines have received
multiple BIOS updates, so they're not running the original
BIOS file any more.

This dropping dead problem, used to be random, and might show up
once a week, or it can go a month without doing it. In this particular
case, this was a reproducible instance of the behavior, basically
happening around 60 seconds after boot. No, it's not LSASS/CSRSS
as they were still running, and they were running when I used
the other profile. I could also run on my daily Profile while
in Safe Mode (I have the F8 Safe Mode in the boot menu to use).

I've changed processor, video card, NIC (switched off the RealTek which
would stop working after boot). This changes the frequency of occurrence
a bit, but did not cure the problem.

A couple of times, Windows "recovered", suggesting it might be the
NVidia containerized video driver doing it. But the odds of it recovering
are relatively poor. Most of the time, it turns off screen, power to mouse, power to keyboard (the +5VSB supply).

Now that I've Repair Installed it, it's running like a top again, but
give it a month, the gremlin will be back.

If it would leave an Event, or some sort of message, I'd have something
to work with. It leaves nothing, except a reminder the previous
shutdown was dirty (as all you can do after this happens, is RESET
or POWER OFF).

Paul


--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

"...w¡ñ§±¤ñ" wrote:

No impact on 26H2 W11 Pro on this device when changing setting from Auto
to Small or Large(i.e. your 'Big' term).

Also note, Auto on this device configures the same as Small.
 i.e. Auto or Small - exact same condition

Presumably "auto" will vary depending e.g. whether you plug a 4K monitor
into a small laptop?
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 10/11/2026 5:05 AM, Andy Burns wrote:

"...w¡ñ§±¤ñ" wrote:

No impact on 26H2 W11 Pro on this device when changing setting from
Auto to Small or Large(i.e. your 'Big' term).

Also note, Auto on this device configures the same as Small.
  i.e. Auto or Small - exact same condition

Presumably "auto" will vary depending e.g. whether you plug a 4K monitor into a small laptop?

Yes, Auto will vary based on the monitor size and display resolution.

As I noted - 'on this device'[laptop, 1080p 15.6 display], the two
settings are the same.
=> Auto by design defaults to Small size without making any other
adjustment attempts, yet the setting for each is select-able and remains configured(after selection)
--
...w¡ñ§±¤ñ
--- Synchronet 3.21d-Linux NewsLink 1.2