Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer error 2755 / 1603 / 1703 #1870

Closed
diegocr opened this issue Mar 19, 2019 · 11 comments
Closed

Installer error 2755 / 1603 / 1703 #1870

diegocr opened this issue Mar 19, 2019 · 11 comments

Comments

@diegocr
Copy link

@diegocr diegocr commented Mar 19, 2019

Hello,

Since build 190108 i'm facing the following problem, which i decided to ignore... but right now i got a notification about a new 190310 version and again the same issue.

So... that also means 130108 was apparently silently installed at some point (just realized that's the version i'm currently using), and hence may happens the same with this 190310 but i thought on reporting this in any case...

191219205300

This generated a ConEmu.190310.213501453.log file containing the following.

ConEmu Setup 190310 on 2019-3-19 21:35:01
OS Version: 6.3 (build 9600) 
Command line: `"R:\ConEmuSetup.190310.exe" `
Current dir: `R:\Temp\ConEmu190310`
GetTempPath: `R:\Temp\`
Environment variables:
---REMOVED---


ConEmu 190310 installer
Installer failed
R:\Temp\ConEmu190310\ConEmu.190310.x64.msi
ExitCode=1603
ReportError code=1703

Any hint on what's going on here please?

Thanks in advance.

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Mar 19, 2019

This looks like a common problem of msi, not related to ConEmu.
Googling: https://appuals.com/how-to-fix-error-code-2755-when-installing-programs-or-applications/

Loading

@diegocr
Copy link
Author

@diegocr diegocr commented Mar 20, 2019

Sorry about that, and thanks for googling for me.

Nothing of that worked though, i did however ran sfc /scannow which did found problems such as:

00000a3b [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

That issue got resolved then by running the following commands as explained here:

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth

Although afterwards still the same 2755 error attempting to install ConEmu.

Will try to do some more research about this and can post results of how it went if interested, if not feel free to close this as obvious off-topic.

Thanks.

Loading

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Mar 20, 2019

Does folder "Windows/Installer" exist?
Does any other msi work?

Try to unpack Installer files (call "ConEmuSetup.exe /?" for switches) and run msi file from explorer.

Loading

@diegocr
Copy link
Author

@diegocr diegocr commented Mar 20, 2019

That did the trick! unpacking the installer files and running the msi installed it properly, thanks a ton 🙇‍♂️

PS: Answering your questions, yeah i do have "Windows/Installer"...although i had that folder compressed.. i turned that thing off before running the dism commands above, which didn't helped to resolve the issue. (and no other msi at hand to test sorry, i don't usually install new software on this machine)

Loading

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Mar 20, 2019

I have no more ideas what happens in your side.
ConEmuSetup just unpacks files (same as you have done manually) and runs msi.
It's interesting what will happen with next it previous build of ConEmuSetup? Will it fails again?
If so, comparing command lines of msi for failed and succeeded runs may help.

Loading

@diegocr
Copy link
Author

@diegocr diegocr commented Mar 21, 2019

Well, fwiw i have a few Windows folders symlinked to a RAMDisk, not sure whether the installer is finding some of those folders are behind a symlink/junction and choking on them?

image

Anyway, i am happy i was able to install the last version, let's see what happens the next time :)

Loading

@diegocr
Copy link
Author

@diegocr diegocr commented Mar 30, 2019

FYI: Attempting to upgrade to 190326 using the same manual extraction method just realized that if i do this from the RAMDisk it does fail with the same 2755 error, however if i do move the *.msi file to a normal HDD then it does work fine, ha!

Of course this only started happening recently, so perhaps some Windows update(s) is causing this now, been using the RAMDisk for ages, under Windows 8.1

For the RAMDisk i'm using ImDisk Toolkit from https://sourceforge.net/projects/imdisk-toolkit/

Loading

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Mar 31, 2019

I think the environment variable TEMP points to your RAM disk? ;)

Loading

Maximus5 pushed a commit that referenced this issue Mar 31, 2019
  Ability to specify temparary directory for msi files.
  So, you may specify on the ‘Update’ settings page special
  installer command, e.g.: `"%1" /t:"C:\Temp\ConEmuFiles"` /p:%3,adm /qn`.
  If the switch `/t:...` is not specified, Setupper uses:
  * `TEMP` environment variable;
  * `GetTempPath` API function if variable is not defined.
@Maximus5 Maximus5 added this to the 190325 milestone Mar 31, 2019
@Maximus5 Maximus5 added this to To Do in ConEmu via automation Mar 31, 2019
@Maximus5 Maximus5 moved this from To Do to Ready for Testing in ConEmu Mar 31, 2019
@diegocr
Copy link
Author

@diegocr diegocr commented Mar 31, 2019

Correct, TEMP resolves to R:\Temp which is the RAMDisk indeed :)

I see you're making changes to allow specifying the temp path, thanks for that!

Loading

@diegocr
Copy link
Author

@diegocr diegocr commented Mar 31, 2019

Looks like i submitted my previous post while you was releasing a new version :)

FYI: This did work: ConEmuSetup.190331.exe /t:C:\Temp /p:x64 /qr

while this did not (the msi still went to TEMP): ConEmuSetup.190331.exe /t:"C:\Temp" /p:x64 /qr

Loading

@flowswitch
Copy link

@flowswitch flowswitch commented May 21, 2019

Same issue with v190331, using RAMDisk too, but this is the first time I see this kind of problems with it in many years of usage. /t switch helps.

Loading

@Maximus5 Maximus5 closed this May 22, 2019
ConEmu automation moved this from Ready for Testing to Done May 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
ConEmu
  
Done
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants