Tron script rolls back to Windows 11 Classic Command bar

[Rayden-Berzerk409]

Hi.
I'm using Tron script latest version on Windows 11 22H2 (22621.3880), and after full execution, and after rebooting, after opening File Explorer I see Tron rolled back to Classic Windows 11 command bar, and disables the new design of the File Explorer with Tabs.
I usually like the new design rather than the legacy one, but I see Tron disables it.
And I know it's Tron because I already ran another 7 scripts for debloating and optimizing, and after execution, those scripts didn't disable the new design of File Explorer with tabs.
I really hope that if new version is uploaded, Tron implements a way to let user select if they want the legacy File Explorer design (Windows 11 22H2+) or want to stay in the modern one.

[vocatus]

Hi @Rayden-Berzerk409 , if you manually launch O&O ShutUp10 (in tron/resources/stage_4_repair/disable_windows_telemetry), does it allow you to change the design back?

This isn't intentional behavior by Tron, I suspect it may be a change that O&OShutUp10 makes.

[Git-North]

I'm having the same problem

[Git-North]

restoring o&o to default settings did not fix the problem.

[Git-North]

Could this be related to the removal of "modern apps"?

[Git-North]

@vocatus please re-open this sissue

[dodo3142]

@Git-North did you fix it ?

[danielsjam]

The changes was made to my system as well. Since Tron didn't find anything on my system, I used the restore point that was created to get my system back to the state before I ran Tron. I hated the Win 11 context menu and explorer when I first started using Win 11, but have learned to like the change. I didn't like the change back to the classic menus and explorer. The other issue I ran across is when TDSSKiller run, it tries to install a driver in the windows\system32\drivers directory. Each time TDSSKiller is run, the name of the driver file changes (1st run 41022176.sys, 2nd run 44003320.sys). I did run it a 3rd time from the stage_0_prep directory, but didn't write down the driver name, but it was different from the two above. No sure if this is normal. The driver was blocked by Norton 360.

[vocatus]

Hi everyone, apologies I've been out for the holidays.

@danielsjam Tron documentation explicitly states to disable ALL anti-virus programs BEFORE running Tron. Also, why you'd be running Norton in the year 2025 is .... baffling. Windows Defender is more than sufficient these days. I'd strongly recommend uninstalling all Norton products from your machine.

@Git-North, I'm looking at this now.