Page Comparison

Contents

...

If a proxy server is configured, it will be displayed in the command output.

Powershell:

$proxySettings = Get-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'

if ($proxySettings.ProxyEnable -eq 1)

{

Write-Output "Proxy Server: $($proxySettings.ProxyServer)"

}

else {

Write-Output "Proxy is not enabled."

}

If proxy is set, this will be the result:

...

If you have no proxy set, but the logs still show proxy, please run
netsh winhttp show proxy in CMD as Admin.

...

dsRequester can’t be installed

When encountering error 1603 with the message "running scripts is disabled on this system," follow these steps to resolve the issue:

MSI (s) (10:5C) [09:52:57:625]: Executing op: CustomActionSchedule(Action=ca_registerTasks,ActionType=3073,Source=BinaryData,Target=WixQuietExec64,CustomActionData="PowerShell.exe" -Command "Import-Module 'C:\Program Files\WindowsPowerShell\Modules\gytpolServer\gytpolServer.psm1' -Force; Register-gytTasks" "eyJneXRTZXJ2ZXJVcmlNYXNrIjoiaHR0cHM6Ly92dDYxZXp0NHE2LmV4ZWN1dGUtYXBpLnVzLWVhc3QtMi5hbWF6b25hd3MuY29tL3Byb2QvIiwiZ3l0U2VydmVyQXBpS2V5IjoiWUNVcmFiTTFjWDV4WkR4NE1uR3IzYkRJS1ZyUVA2ODFFMWJsS3R1YSJ9")
MSI (s) (10:5C) [09:52:57:625]: Creating MSIHANDLE (74) of type 790536 for thread 8284
MSI (s) (10:B0) [09:52:57:625]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIE313.tmp, Entrypoint: WixQuietExec64
MSI (s) (10!6C) [09:52:58:460]: Creating MSIHANDLE (75) of type 790531 for thread 8556
WixQuietExec64: Import-Module : File C:\Program Files\WindowsPowerShell\Modules\gytpolServer\gytpolServer.psm1 cannot be loaded
MSI (s) (10!6C) [09:52:58:460]: Closing MSIHANDLE (75) of type 790531 for thread 8556
MSI (s) (10!6C) [09:52:58:475]: Creating MSIHANDLE (76) of type 790531 for thread 8556
WixQuietExec64: because running scripts is disabled on this system. For more information, see about_Execution_Policies at
MSI (s) (10!6C) [09:52:58:475]: Closing MSIHANDLE (76) of type 790531 for thread 8556
MSI (s) (10!6C) [09:52:58:475]: Creating MSIHANDLE (77) of type 790531 for thread 8556
WixQuietExec64: https:/go.microsoft.com/fwlink/?LinkID=135170.

To resolve Error 1603 with "Running Scripts is Disabled on this System"

When encountering error 1603 with the message "running scripts is disabled on this system," follow these steps to resolve the issue:

Step 1: Change the PowerShell Execution Policy

1. Open PowerShell as Administrator:

   • Click on the Start menu.

   • Type powershell.

   • Right-click on Windows PowerShell and select "Run as administrator."

2. Set the Execution Policy:

   • In the PowerShell window (running as administrator), type one of the following commands and press Enter:

     • For RemoteSigned (scripts created locally are allowed, remote scripts need to be signed):

       Code Block
       powershell

       Copy code

       Set-ExecutionPolicy RemoteSigned

     • For Unrestricted (all scripts are allowed to run for testings):

       Code Block
       powershell

       Copy code

       Set-ExecutionPolicy Unrestricted

3. Confirm the Change:

   • If prompted, type Y and press Enter to confirm the change.

Step 2: Modify Group Policy Settings

1. Open Group Policy Editor:

   • Press Win + R to open the Run dialog.

   • Type gpedit.msc and press Enter.

2. Navigate to PowerShell Settings:

   • In the Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.

3. Ensure Script Execution is Allowed:

   • Locate the "Turn on Script Execution" policy.

   • Ensure it is set to "Not Configured" or "Enabled" with an appropriate execution policy that allows script execution.

   • Image Added

Step 3: Additional Troubleshooting (if needed)

1. Disable Antivirus Temporarily:

   • Temporarily disable your antivirus software and try running the installer again.

2. Run Installer as Administrator:

   • Right-click the installer and select "Run as administrator."

3. Clear Temporary Files:

   • Delete temporary files from %temp% and C:\Windows\Temp.

4. Restart Windows Installer Service:

   • Open the Run dialog (Win + R), type services.msc, and press Enter.

   • Locate "Windows Installer," right-click it, and select "Restart."

Anchor
_Toc141005933 _Toc141005933

Client can’t be upgraded

...