privacy.sexy
privacy.sexy copied to clipboard
Some installer failed to installer
On a newly installed Windows 10 pro, select mode Strict
, tweak a little, apply.
After that, some installers fails to install, screenshot as below, how to recover?
When run the installer in a terminal window with admin priviledge, it succeedes.
Hi @playgithub , thanks for the bug report. Let's track this down and fix it.
-
Could you provide logs from windows installer? See here for a nice way to get the logs.
-
Please provide the script you executed, and share your OS version.
The failed installer might be either .exe or .msi.
For python it is exe, I've uninstalled it, and reinstall python-3.9.6-amd64.exe /log log.txt
in terminal without admin priviledge, it succeeds. I think it might only fail for the first time, because it needs some priviledge to initialize something.
OS: Windows 10 Pro 21H1 19043.1165
I'll open another issue when I can't get the log with failures.
Thanks
- In admin terminal it'll succeeds
- Double click installer in File Explorer, it it fails during the installation, error code 2503
The installer will ask "Disable Do you want to allow this app to make changes to your device?"
Choose "Yes" and continue, after a while error 2503 occurs.
C:\Windows\TEMP
is cleared before installation, when the error occurs, screenshot as below - In non-admin terminal it fails as below
λ msiexec.exe /i .\LibreOffice_7.1.6_Win_x64.msi /L*v install.log λ cat install.log □□=== Verbose logging started: 10/1/2021 09:46:26 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\system32\msiexec.exe === MSI (c) (D0:8C) [09:46:26:966]: Font created. Charset: Req=0, Ret=0, Font: Req=, Ret=Arial MSI (c) (D0:8C) [09:46:26:966]: Font created. Charset: Req=0, Ret=0, Font: Req=, Ret=Arial MSI (c) (D0:9C) [09:46:26:966]: Resetting cached policy values MSI (c) (D0:9C) [09:46:26:966]: Machine policy value 'Debug' is 0 MSI (c) (D0:9C) [09:46:26:966]: ******* RunEngine: ******* Product: .\LibreOffice_7.1.6_Win_x64.msi ******* Action: ******* CommandLine: ********** MSI (c) (D0:9C) [09:46:26:966]: Machine policy value 'DisableUserInstalls' is 0 MSI (c) (D0:9C) [09:46:26:981]: Note: 1: 1324 2: . 3: 1 MSI (c) (D0:9C) [09:46:26:981]: MainEngineThread is returning 2 === Verbose logging stopped: 10/1/2021 09:46:26 ===
Windows 10 21H2 Build 19044.1586 privacy.sexy 0.11.4 (option Standard)

By allowing the current user to modify and write to C:\Windows\temp
, the problem is solved.
Which script causes the problem?
Can confirm I had the same issue On Windows 11 Pro (22H2), creating the folder C:\Windows\temp
resolved it for me.
i also had the same issue. it seems something is deleting C:\windows\temp
im sorry im not more proficient in the background processes etc, but i used the "standard" set of scripts, using the offline installer.
creating a new temp folder was the fix.
Thank you for the report @freighttt and @lintonf ,
So then it's this script causing the problem:
name: Clear Windows temp files
recommend: standard
code: |-
del /f /q %localappdata%\Temp\*
rd /s /q "%WINDIR%\Temp"
rd /s /q "%TEMP%"
And this PR #176 by @iam-py-test seems to resolve this issue. So I'll ensure that PR is merged in upcoming patch releases. We can track the status there.