The GUI doesn't open

[amethyze]

Describe the Bug

Whenever I try to open the GUI script just like it says on the wiki, it starts to output lots of error messages, and then it closes

How can this issue be reproduced?

1. Run the GUI like its specified on the README
2. See the error

Expected behavior?

The GUI should appear.

Operating System

Windows 10

Operating System Version

22H2

Screenshots

Logs

No response

Additional Info

No response

[LeDragoX]

You're in the wrong location C:\Windows\System32\ It should be on the same folder as the script... ...or something went* really wrong, before you hit enter, what was the directory you were?

[amethyze]

Am I supposed to be in C:\Windows\System32? Because I was on a folder I had just created with all the files in it

On February 26, 2023 12:38:03 PM GMT-05:00, "Plínio Larrubia" @.***> wrote:

You're in the wrong location C:\Windows\System32\ It should be on the same folder as the script... ...or something is really wrong, before you hit enter, what was the directory you were?

-- Reply to this email directly or view it on GitHub: https://github.com/LeDragoX/Win-Debloat-Tools/issues/89#issuecomment-1445416768 You are receiving this because you authored the thread.

Message ID: @.***>

[LeDragoX]

The error may be related to permissions, because on this command:

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force; ls -Recurse *.ps*1 | Unblock-File; .\"Win10ScriptGUI.ps1"

The Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force; Allow your user to run Powershell scripts And ls -Recurse *.ps*1 | Unblock-File; will make each child file with ".ps1,psm1" as extension to be able to execute without the need to press R and ENTER to import modules and run the needed functions.

The last one .\"Win10ScriptGUI.ps1" on the main branch is just to run the script which generates the GUI and allows mouse interactivity.

Can you send a log within the folder %temp%\Win-DT-Logs? In these case scenarios, logs will allow me to see from start to finish what happened.

[amethyze]

It didn't output any logs at all, that's not normal, is it?

On February 27, 2023 1:45:01 PM GMT-05:00, "Plínio Larrubia" @.***> wrote:

The error may be related to permissions, because on this command:

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force; ls -Recurse *.ps*1 | Unblock-File; .\"Win10ScriptGUI.ps1"

The Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force; Allow your user to run Powershell scripts And ls -Recurse *.ps*1 | Unblock-File; will make each child file with ".ps1,psm1" as extension to be able to execute without the need to press R and ENTER to import modules and run the needed functions.

The last one .\"Win10ScriptGUI.ps1" on the main branch is just to run the script which generates the GUI and allows mouse interactivity.

Can you send a log within the folder %temp%\Win-DT-Logs?

-- Reply to this email directly or view it on GitHub: https://github.com/LeDragoX/Win-Debloat-Tools/issues/89#issuecomment-1446867172 You are receiving this because you authored the thread.

Message ID: @.***>

[LeDragoX]

It didn't output any logs at all, that's not normal, is it?

Ok, then it didn't even started properly. I don't know.

Have you really done each step from README?

1. Download a version
2. Extract the .zip folder somewhere
3. Run OpenTerminalHere.cmd which opens a new powershell window in your case, but already on the correct directory.
4. Run the command to use GUI or CLI (the entire line).

If this isn't the case, i recommend trying something different, like trying to unlock powershell to Local Machine

Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force; ls -Recurse *.ps*1 | Unblock-File; .\"Win10ScriptGUI.ps1"

If something is wrong in the step 3, you can force OpenTerminalHere.cmd to run as admin, then it will work normally.

And if even that doesn't work, you can download the Develop version, which was really improved recently...but that is your last resort.

[amethyze]

You have to extract the entire zip? That's probably why it didn't work. I only extracted the .cmd and the .ps1 files.

On February 28, 2023 6:40:08 AM GMT-05:00, "Plínio Larrubia" @.***> wrote:

It didn't output any logs at all, that's not normal, is it?

Ok, then it didn't even started properly. I don't know.

Have you really done each step from README?

1. Download a version
2. Extract the .zip folder somewhere
3. Run OpenTerminalHere.cmd which opens a new powershell window in your case, but already on the correct directory.
4. Run the command to use GUI or CLI (the entire line).

If this isn't the case, i recommend trying something different, like trying to unlock powershell to Local Machine

Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force; ls -Recurse *.ps*1 | Unblock-File; .\"Win10ScriptGUI.ps1"

If something is wrong in the step 3, you can force OpenTerminalHere.cmd to run as admin, then it will work normally.

And if even that doesn't work, you can download the Develop version, which was really improved recently...but that is your last resort.

-- Reply to this email directly or view it on GitHub: https://github.com/LeDragoX/Win-Debloat-Tools/issues/89#issuecomment-1448034768 You are receiving this because you authored the thread.

Message ID: @.***>

[LeDragoX]

You have to extract the entire zip? That's probably why it didn't work. I only extracted the .cmd and the .ps1 files.

Yes!!! 🤣🤣🤣 You should extract the entire zip to the script work, it's not a standalone file like other scripts from the community.