|
|
Post by anixx on Jun 22, 2019 16:37:33 GMT -8
Here is a method which allows to enable and disable Classic Theme during one session from the command line. Tested on Windows 8.1. Enabling or disabling the Classic theme affects only programs started after the change. Steps: 1. Install PowerShell 6: github.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x64.msigithub.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x86.msi2. Run PowerShell 6 and type: Install-Module -Name NtObjectManager 3. Now you can enable and disable Classic Theme. To enable, open elevated command prompt and type: pwsh -c Set-NtSecurityDescriptor -path \"\Sessions\$([System.Diagnostics.Process]::GetCurrentProcess().SessionId)\Windows\ThemeSection\" \"O:BAG:SYD:(A;;RC;;;IU)(A;;DCSWRPSDRCWDWO;;;SY)\" Dacl To disable, open elevated command prompt and type: pwsh -c Set-NtSecurityDescriptor -path \"\Sessions\$([System.Diagnostics.Process]::GetCurrentProcess().SessionId)\Windows\ThemeSection\" \"O:BAG:SYD:(A;;CCLCRC;;;IU)(A;;CCDCLCSWRPSDRCWDWO;;;SY)\" Dacl |
|
|
|
Post by R.O.B. on Jun 24, 2019 19:12:47 GMT -8
Marvelous work, anixx! Well done! This is very useful! Perhaps it can be used to “whitelist” which programs use the classic theme by launching them with a script? That would be incredibly useful for software that refuses to work properly (or at all) with the classic theme. |
|
|
|
Post by anixx on Jun 25, 2019 3:22:32 GMT -8
Marvelous work, anixx ! Well done! This is very useful! Perhaps it can be used to “whitelist” which programs use the classic theme by launching them with a script? That would be incredibly useful for software that refuses to work properly (or at all) with the classic theme. Note that the bracketed part with IU (Interactive User) affects the user's software, while the part with SY (System) on Windows 8.1 affects the UAC prompt. Since on Win10 UAC prompt is immersive, it is likely would not be affected, so the parts with SY can be omitted. |
|
|
|
Post by Aesthetic Classic on Jul 12, 2019 7:17:11 GMT -8
This is nice considering you can reverse it if you ever need to run a UWP app or restart Explorer without having to log off. It's better than the ObjDir method as this also works with the file browser dialogs (Open, Save As...) in newly opened programs.
|
|
Fierelier
Freshman Member
Posts: 35 
OS: Windvn Daedalus (Devuan)
Theme: gtk-theme-raleigh
CPU: i5-520M
RAM: 4GB
GPU: Intel HD (Gen5)
|
Post by Fierelier on Jul 14, 2019 9:05:22 GMT -8
This works fantastically in Windows 10 1809, nice work!
|
|
|
|
Post by anixx on Jul 14, 2019 18:53:31 GMT -8
This is nice considering you can reverse it if you ever need to run a UWP app or restart Explorer without having to log off. It's better than the ObjDir method as this also works with the file browser dialogs (Open, Save As...) in newly opened programs. It should be the same as ObjDir in this respect. |
|
|
|
Post by grinder2018 on Jul 15, 2019 23:16:31 GMT -8
Some one test it with 1903?
Can i see a screen shot?
Thanks
|
|
|
|
Post by faenus on Jul 24, 2019 22:04:24 GMT -8
How do I get the win 7 color control panel on windows 10 ?
Used to be something like "C:\Windows\system32\rundll32.exe" Shell32.dll,Control_RunDLL desk.cpl ,@advanced or "control color" but they don't work anymore in 1809
|
|
|
|
Post by papo on Aug 17, 2019 9:16:17 GMT -8
When I enable Classic Theme with:
pwsh -c Set-NtSecurityDescriptor -path \"\Sessions\$([System.Diagnostics.Process]::GetCurrentProcess().SessionId)\Windows\ThemeSection\" \"O:BAG:SYD:(A;;RC;;;IU)(A;;DCSWRPSDRCWDWO;;;SY)\" Dacl
the answer in red color:
At line:1 char:80
+ ... riptor -path \\Sessions\2\Windows\ThemeSection\ \O:BAG:SYD:(A;;RC;;;I ...
+ ~
Missing closing ')' in expression.
At line:1 char:89
+ ... th \\Sessions\2\Windows\ThemeSection\ \O:BAG:SYD:(A;;RC;;;IU)(A;;DCSW ...
+ ~
Unexpected token ')' in expression or statement.
At line:1 char:92
+ ... \\Sessions\2\Windows\ThemeSection\ \O:BAG:SYD:(A;;RC;;;IU)(A;;DCSWRP ...
+ ~
Missing closing ')' in expression.
At line:1 char:113
+ ... s\ThemeSection\ \O:BAG:SYD:(A;;RC;;;IU)(A;;DCSWRPSDRCWDWO;;;SY)\ Dacl
+ ~
Unexpected token ')' in expression or statement.
+ CategoryInfo : ParserError: ( : ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingEndParenthesisInExpression
The Classic Theme don't appear (after Win restart). My Op: Win10/64, version 1903. What could be the problem?
|
|
|
|
Post by anixx on Aug 18, 2019 7:44:38 GMT -8
Maybe you did not install PowerShell 6 or the module NtObjectManager.
Or you are running that command from PowerShell, not from Command Prompt.
|
|
|
|
Post by papo on Aug 20, 2019 9:42:55 GMT -8
Maybe you did not install PowerShell 6 or the module NtObjectManag. Or you are running that command from PowerShell, not from Command Prompt. Thanks. Unfortunately, it still fails. PowerShell 6 and NtObjectManager are both installed here: C: \ Program Files \ WindowsPowerShell \ Modules \ NtObjectManager \ Running the command as a elevated administrator command prompt:
C:\>pwsh -c Set-NtSecurityDescriptor -path \"\Sessions\$([System.Diagnostics.Process]::GetCurrentProcess().SessionId)\Windows\ThemeSection\" \"O:BAG:SYD:(A;;RC;;;IU)(A;;DCSWRPSDRCWDWO;;;SY)\" Dacl
Set-NtSecurityDescriptor : The term 'Set-NtSecurityDescriptor' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Set-NtSecurityDescriptor -path "\Sessions\$([System.Diagnostics.Proce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Set-NtSecurityDescriptor:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
|
|
|
|
Post by anixx on Aug 20, 2019 11:20:47 GMT -8
NtObjectManager should be installed into another place. Install it with the command I described.
|
|
|
|
Post by papo on Aug 20, 2019 11:54:36 GMT -8
NtObjectManager should be installed into another place. Install it with the command I described. Thanks for the help. Sorry. Resolved the issue: it was not PowerShell 6 running, but an older version of Windows (this does not print the version number when running). This way the ObjectManager installation and the command in CMD were executed without any errors. I restarted the machine, but I don't see any change in appearance. Everything remained the same. |
|
|
|
Post by anixx on Aug 20, 2019 13:11:49 GMT -8
NtObjectManager should be installed into another place. Install it with the command I described. Thanks for the help. Sorry. Resolved the issue: it was not PowerShell 6 running, but an older version of Windows (this does not print the version number when running). This way the ObjectManager installation and the command in CMD were executed without any errors. I restarted the machine, but I don't see any change in appearance. Everything remained the same. No surprise. After restart everything will reset to default. Where did you read you should restart? |
|
|
|
Post by jevilogen on Sept 18, 2019 7:18:27 GMT -8
i typed in "Install-Module -Name NtObjectManager" and it said "Oops, something went wrong. Please report this bug with the details below."
|
|
SemoB
New Member
Posts: 10
OS: Windows 10 Education 1909
Theme: WindowBlinds - The Classic Theme
|
Post by SemoB on May 5, 2020 9:35:34 GMT -8
Hi I have tried this method on Windows 10 1909 but I get the following error: Get-NtObject : The type initializer for 'NtApiDotNet.NtType' threw an exception. At C:\Users\Isam\Documents\PowerShell\Modules\NtObjectManager\1.1.27\NtObjectManager.psm1:2652 char:37 + ... ject($obj = Get-NtObject -Path $Path -TypeName $TypeName -Access $acc ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (  [Get-NtObject], TypeInitializationException + FullyQualifiedErrorId : System.TypeInitializationException,NtObjectManager.GetNtObjectCmdlet Any ideas? Thank you. |
|
|
|
Post by ihatemetro on Oct 11, 2020 7:48:42 GMT -8
I get this on 1903: Get-NtObject : The type initializer for 'NtApiDotNet.NtType' threw an exception. At I:\Documents\PowerShell\Modules\NtObjectManager\1.1.28\NtObjectManager.psm1:3078 char:37 + ... ject($obj = Get-NtObject -Path $Path -Root $Root -TypeName $TypeName ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: ( [Get-NtObject], TypeInitializationException + FullyQualifiedErrorId : System.TypeInitializationException,NtObjectManager.Cmdlets.Object.GetNtObjectCmdlet Why do all Classic Theme options that appeal to me throw an error? |
|
|
|
Post by travis on Oct 11, 2020 18:18:06 GMT -8
I got the same error.
|
|
|
|
Post by katieboundary on May 17, 2021 9:25:25 GMT -8
What is an "elevated" command prompt and how do I open one?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 17, 2021 11:30:35 GMT -8
What is an "elevated" command prompt and how do I open one? Elevated command prompt is command prompt but with administrator permissions, allowing you to almost run more commands than the normal mode. And yes, there are many ways to open one: 1- Either press Win+X on your keyboard (or right click on start button [only if you're running windows 8 or 10, and that you have the "Replace Command Prompt with Windows PowerShell" off {in the navigation tab in windows 8 and 8.1, and also in the settings app in windows 10]) and select "Command Prompt (Admin)" option. 2- Pressing the start menu and typing cmd in the search box and right clicking on it and select "Run as administrator" with the shield icon. |
|
[Get-NtObject], TypeInitializationException
