LTSC 'RIBBON'???? - Again!

[scaramonga]

Further to my thread about enabling new features on LTSC.

S

Thread 'W11 LTSC - Enabling new features'

Sep 14, 2026

Latest 9539 version image, (9445 & 9457 same)

Trying to enable the following:

I unlocked the Windows 11 September 2026 update early, and here's how you can too

KB5120998 – Windows 11's September 2026 update adds new features, but Microsoft is rolling them out gradually. Here's how to unlock them with ViveTool.

pureinfotech.com

id:61161244 (All), results in the following mish-mash, aka features enabled, but has the adverse effect of adding back the 'ribbon' in file explorer, along with removing 'tabs', and limiting the 'right click menu'? WTF!?

Any other 'id' from above added individually, does nothing?

id:62353331,62762248,61754985, nor id:59213768,61090762 do nothing either?

Is this a case of 25H2/26H2 'enablement package' not being...

• scaramonga
• Replies: 13
• Forum: Questions and Reports

That thread can be deleted if desired, as this problem still persists without going anywhere near enablement ID's.

I decided to integrate latest (9550) on image: 'en-gb_windows_11_enterprise_ltsc_2024_x64_dvd_e2137661' tonight, with the standard 'preset' I have used forever, no changes.

Upon first boot, I'm greeted with the 'ribbon' in file explorer, and the 'limited' right click menu again???, upon activation, it remains the same. Why is this 'ribbon' even here now?

Nothing done to system, it presents itself as just that?, activated or not.

(9457) does not, and I have it running in VM with no 'ribbon', nor 'right click' nonsense?, can anyone put their finger on this please?

It IS keeping me awake @ nights.

 

[crypticus]

Hi this issue is related to:

Microsoft AIFabric CBS 1.6 and Microsoft.WindowsAppRuntime.CBS.2 ("Windows App Runtime v2") keep them or wait for fix

also microsoft error reporing has problems right now keep it too if you delete normally. nuhi will fix these hopefully this week

 

[garlin]

When Recall first appeared in 2024, there was a similar bug where if Client.CBS.AIX was disabled or removed, WindowsAppRuntime wasn't properly registered as a library. Without it, you get the raw UI underneath which is the legacy UI.

It's probably a similar bug.

 

[crypticus]

probably u are right, I'm also amazed that we can't remove click to do (as it was seperated from recall feature) nuhi

 

[scaramonga]

Hi this issue is related to:

Microsoft AIFabric CBS 1.6 and Microsoft.WindowsAppRuntime.CBS.2 ("Windows App Runtime v2") keep them or wait for fix

also microsoft error reporing has problems right now keep it too if you delete normally. nuhi will fix these hopefully this week

Hi. Thanks! Seems to work, so progress, lol Although irritating MS again with its 'remove something, break something'.

I also noticed there is 'UI Ribbon' in components, can't recall seeing that before. In screen below. It's enabled by default.

 

[crypticus]

Yes, more you remove, more headache you got. I wouldn't remove that it might be about elements on ribbon especially shown when you expand it.

 

[chrcol]

Haha thats an improvement over the default UI.

The only thing I really remove is that backup feature, because it nags if you leave it in place, I do disable (not remove) recall, although I have noticed its default state now reports disabled.

In terms of the CU, I can see myself just staying on July 2026 CU, once I am on 11 for daily use, I think my need to have something that works, will prevent me from ever updating, it would need to be a serious remote exploit (cannot remember last time windows had one, its all nonsensical local exploits now that have millions people in fear) or a major feature I want.

The OS is so fragile, the amount of issues, some of them quite nasty I am having to resolve is an eye opener, when I went from 8.1 to 10, within 3 days of starting work on my ISO, I was using it daily. 10 to 11 is far more challenging.

 

[scaramonga]

https://www.neowin.net/news/removewindowsai-update-script-breaks-windows-11-file-explorer-ui/#login-form

Sounds familiar.

 

[garlin]

The original fix was to confirm Microsoft.WindowsAppRuntime.CBS_cw5n1h2txyewy is still one of your installed packages, after removing AI features.

 

[scaramonga]

Installing Microsoft.WindowsAppRuntime.CBS_cw5n1h2txyewy alone does not cure the problem. Keeping AIFabric CBS 1.6 does. Why?

 

[garlin]

I remember abbodi said it's something-something in the AI features install that registers WindowsAppRuntime.CBS. And when you don't have the feature, Windows doesn't have a fallback method.

With Recall, if you ended up with the W10 Classic Ribbon the fix was to temporarily enable Recall (registering CBS) and then disable Recall. The disable didn't have any steps which would uninstall CBS There wasn't a specific fix to register CBS on its own, so you borrowed the enable step to properly install the framework.

I dunno. Go ask abbodi.

 

[crypticus]

thread mentions something about

HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\1561856655 EnabledState to 1

so this would fix the issue if u keep appruntimecbs installed? Is that what nuhi fixed in new versions of ntlite?

 

[tistou77]

Since the Preview (9550) you need to keep CBS v2 instead of CBS v1.6 for "Open with" to work (as well as AI Fabric, though only within the image).
MS changed something regarding this option, they may have also made changes affecting the Explorer ribbon.

 

[crypticus]

yes u are right but now in latest NTLite version u can actually remove AI Fabric and don't break UI or open with (which are tied)

 

[tistou77]

yes u are right but now in latest NTLite version u can actually remove AI Fabric and don't break UI or open with (which are tied)

Yes, I know, Nuhi and I tested that before integrating it into NTLite.
Only the necessary files are kept in the image, as for the "Open with" files, they can be deleted after Windows is installed.
But I haven't tested for the ribbon