Replies: 5 comments 3 replies
-
|
If you're trying to automate it you probably want to run the |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
EDIT: I have found that it seems to do with the fact that Windows restricts powershell scripts by default. The window will just close. I'll see if I can find a workaround without forcing the executionpolicy to an unsafe setting. |
Beta Was this translation helpful? Give feedback.
-
|
@eole73 While playing around a bit I have found a way to do this automatically with one command. In this example I'm running the script with -RunDefaults and -Silent parameters, make sure to add the path to your script root. Start-Process PowerShell -Verb RunAs "-Command `"cd '<PATH_TO_SCRIPT_ROOT_HERE>'; Powershell.exe -ExecutionPolicy Bypass -File './Win11Debloat.ps1' -RunDefaults -Silent;`""Please let me know if this works for you! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help :) . I'm not sure I'll be able to try tomorow but if not I'll definitely try the day after. I suppose it might be possible to replace the -RunDefaults switch by a chosen list of other switches (-arg1 -arg2 ... -argn) ? The way I was launching the script was the following : a powershell command is launching a script I named Win11Debloat_custom.ps1 : This Win11Debloat_Custom.ps1 script is situated in the same directory (Win11Debloat-master) as Win11Debloat.ps1 it is launching. The content of this Win11Debloat_Custom.ps1 script is the following : $argumentList = @("-Silent","-RemoveApps","-RemoveW11Outlook","-RemoveGamingApps","-DisableDVR","-DisableSuggestions","-DisableLockscreenTips","-TaskbarAlignLeft","-ShowSearchIconTb","-HideChat","-DisableWidgets","-DisableCopilot","-DisableRecall","-DisableDesktopSpotlight","-HideTaskview") $scriptArguments = $argumentList -join ' ' $scriptPath="C:\some_path\Win11Debloat-master\Win11Debloat.ps1" Invoke-Expression "& '"$scriptPath'" $argumentList" When I manually execute Win11Debloat_Custom.ps1 it is lauching successfully Win11Debloat.ps1 (a powershell windows opens and all steps are executed successfully and the modifications applied). When I'm running the Win11Debloat_Custom.ps1 script automatically with the powershell command above (the command is executed with SYSTEM rights), the script seems be executed (there seems to be no error interrupting it), but in fact it does not apply the modifications and I get the following output of the powershell command (the one launching Win11Debloat_Custom.ps1) :
Unfortunately, I am not versed enough in powershell to analyze this output :-/. However, the -1 between some tags make me wonder if there might not be some failures during the execution ? I'll try as soon as possible to run the script with the command you provided and let you know if it works. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed reply. How are you automatically calling the script? If the script is run as system, not within user context, then the script will not work as expected. The Win11Debloat's registry changes are applied to the user that executes the script. This would explain your issue. Another possible option is that your custom script is running the script from a different working directory when you're not calling it manually. As the script uses relative paths this might mean the script cannot find/execute the registry files to apply the changes. |
Beta Was this translation helpful? Give feedback.
-
|
The software I use to automate installations/configurations is running with/using python, the powershell command is launched with python functions using among other things the psutil.Popen() method. So the process calling the powershell script is indeed run under the system account. (I tried the powershell command your suggested , but it leads to the same results). It seems to me that the problem is indeed coming from the script being executed with the system account, as when I launch manually the Win11debloat_custom.ps1 script (which is launching Win11debloat.ps1) it does execute successfully. Would there somehow be a possibility to run the Win11debloat.ps1 script under the system account ? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think there's a good way to run the script from the system account, unless you run your script before creating any user account. If you create the windows user account after running the script you could use Win11Debloat SysPrep mode. That mode applies the changes to the default windows user. Any new users would then have Win11Debloat's changes applied to them. If you want the changes to apply to an existing account I would instead suggest to make your script create a RunOnce task in the registry, that will cause the script to run on user login, within the user context. See: https://learn.microsoft.com/en-us/windows/win32/setupapi/run-and-runonce-registry-keys Win11Debloat uses this for applying some changes in Sysprep mode. Example: https://github.com/Raphire/Win11Debloat/blob/master/Regfiles/Sysprep/Hide_Search_Taskbar.reg The above example would be applied to the default user account, if you have just one user account I would suggestion using the local machine runonce. E.g. |
Beta Was this translation helpful? Give feedback.
-
I tried the last two days to execute the script in an automated and silent way (using the -silent switch and other ones of interest) on different W11 machines but to no avail. If I ran the same script manually within a powershell shell on any of these machines, it works but not in an automated way. The script is nevertheless executed with admin rights (using -verb runas in a start-process powershell command) and the execution policy of the local machine scope set to unrestricted (the process scope seems not specifically relevant). Any idea of what could be the problem ?
Beta Was this translation helpful? Give feedback.
All reactions