dcormier

I do see the MSIs being extraced into %temp%\PdnSetup when I run the installer. Process Monitor confirms that PaintDotNet_x64.msi and PaintDotNet_x86.msi are both written to that directory. Again, everything in %temp%\PdnSetup is deleted after the process exits and there's no opportunity to pause before that happens. If I run the installer on another machine, copy the %temp%\PdnSetup directory over, then run PdnSetup\SetupFrontEnd.exe it does seem to work. Should I go ahead with this, or are you (either of you) willing to do more investigation to find out why running the installer doesn't work? I'm leaning towards the latter, since at some point I'll want to do an upgrade and probably won't have another laptop on my desk.

When I run that tool I get this: Here's the pdn.log, which I'm not permitted to attach: === Verbose logging started: 2016-07-07 9:24:18 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\SysWOW64\msiexec.exe === MSI (c) (C8:90) [09:24:18:724]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg MSI (c) (C8:90) [09:24:18:724]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg MSI (c) (C8:54) [09:24:18:735]: Resetting cached policy values MSI (c) (C8:54) [09:24:18:736]: Machine policy value 'Debug' is 0 MSI (c) (C8:54) [09:24:18:736]: ******* RunEngine: ******* Product: PaintDotNetMsi\PaintDotNet_x64.msi ******* Action: ******* CommandLine: ********** MSI (c) (C8:54) [09:24:18:736]: Note: 1: 2203 2: PaintDotNetMsi\PaintDotNet_x64.msi 3: -2147287037 MSI (c) (C8:54) [09:24:18:737]: MainEngineThread is returning 3 === Verbose logging stopped: 2016-07-07 9:24:18 === The PDN installer is in the same directory, with its original name (in case that matters). I enabled MSI logging (set the installer logging registry value to voicewarmupx) and ran the installer normally, but no MSI log was created.

On Windows 10, the installer is silently failing. I already have .Net 4.6.1 installed. I've gone through the install troubleshooting thread, but nothing there has made a difference. PDN was never previously installed on this computer (it's brand new). Here're the contents of pdnSetupShim.log, which I'm not permitted to attach, for whatever reason: --- paint.net SetupShim starting, lpCmdLine='/suppressReboot', nCmdShow=10 CoInitialize(NULL) returned 0 Checking OS requirement bIsWin7SP1 = true bResult = true EnsureOSRequirement() returned 0 Called EnsureTrustedInstallerIsEnabledAsync() Checking .NET requirement bIsNetfx46Installed = true bIsSupportedNetfxInstalled = true bIsNetfxInstallerPresent = true PreInstallPrompt() returned true InstallNetfx() returned 0 Launching paint.net installer. bRebootRequired=false Done. nReturnVal=-1 Sleep(1000) --- Exiting, nReturnVal=ffffffff When I run the installer, it extracts the files it needs, then I see another window open for a fraction of a second and then it all immediately closes. I'm guessing this corresponds to the "Launching paint.net install" and "Done." lines. While everything is being extracted, I can see lots of things being put into %temp%\PdnSetup, but as soon as the program exits it all gets cleaned up. There's no opportunity to pause between when the files are extracted and the program cleans it up and exits. What else should I look at?