|
Post by katieboundary on May 17, 2021 15:31:36 GMT -8
Thanks. That got me this far: What next?
|
|
|
Post by anixx on May 26, 2021 23:27:42 GMT -8
Do you start cmd.exe as admin?
|
|
|
Post by leet on May 27, 2021 5:30:49 GMT -8
It seems so. It says "(Administrator)" in the caption.
|
|
elain
New Member
Posts: 1
|
Post by elain on Aug 7, 2021 12:21:46 GMT -8
Hi, I think I have the same problem, Im stuck with the font but maybe it was because of SCT that I installed after. It was quite buggy and the themes on some windows like the disk formating one has stayed like the one I chose with SCT. Plus that program didnt seem to do anything when I used it, and I sadly would'nt be able to tell the difference with after I used that program and before I used SCT / after I used that program and after I used SCT and deleted it. It might be an SCT issue in the end, so I'll post a screenshot of a text for you to confirm if this is a theme installed with your script. I also tried to change back my font with this website (how to geek) but it didn't work. Thanks for your time and sorry if this is just SCT
|
|
|
Post by hancock on Oct 1, 2022 7:06: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 BitDefender found that NtObjectManager is TROJAN. the command for the elevated command prompt didn't worked, and I couldn't do "Uninstall-Module -Name NtObjectManager". So I wouldn't recommend to use the "NtObjectManager" at all as it has been declared as TROJAN.
|
|
|
Post by anixx on Oct 1, 2022 10:28:31 GMT -8
|
|
|
Post by OrthodoxWin32 on Oct 1, 2022 15:15:06 GMT -8
BitDefender found that NtObjectManager is TROJAN. the command for the elevated command prompt didn't worked, and I couldn't do "Uninstall-Module -Name NtObjectManager". So I wouldn't recommend to use the "NtObjectManager" at all as it has been declared as TROJAN. This is clearly a false positive. Moreover, all the detections of the tools of this forum by antivirus are false positive. Simply because malware has every interest in intervening in the system, but legitimate tools (like the ones in this forum) may also need to intervene in the system. A constructive attitude on your part would be to report the error to BitDefender, so that NtObjectManager is no longer detected. Thanks.
|
|