search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Error 2503 installing brackets on windows 8.1 #6458

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by Sala7ism Sunday Mar 09, 2014 at 08:20 GMT Originally opened as https://github.com/adobe/brackets/issues/7140

Hello

I faced a problem when trying to install brackets on my computer

"The installer has encountered an unexpected error installing the package. This may indicate a problem with this package. The error code is 2503."

I downloaded the last 4 versions from the download page on brackets.io and still get the same error.

Print screen of the error error-2503

core-ai-bot commented 3 years ago

Comment by bchintx Monday Mar 10, 2014 at 16:50 GMT

@Sala7ism I just tested to confirm that both Sprint 32 and 36 download and install just fine on my Win 8.1 system, so the available installers should be OK. Have you tried saving the installer to your hard drive first, and then running the installer from the downloaded location, rather than running it straight from the download page? Also, can you try installing it using the Run as Administrator property?

Are you having any difficulty installing any other application, other than Brackets? I noticed this Microsoft support article that might help in the case that your Windows Installer Service is the culprit: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-codes-2503-2502-while-unistall-or-install-a/6a996faf-7e28-40bd-b5e0-02ab17dfcd88

core-ai-bot commented 3 years ago

Comment by dangoor Wednesday Mar 19, 2014 at 18:01 GMT

Reviewed low priority to@bchintx (raise the priority if we start seeing more)

core-ai-bot commented 3 years ago

Comment by wizAmit Monday Mar 24, 2014 at 20:51 GMT

I installed Brackets on my win8.1 and it installed just fine. also i worked according to docs and it built successfully.

core-ai-bot commented 3 years ago

Comment by peterflynn Thursday Jan 08, 2015 at 22:10 GMT

Closing since we never heard back from the filer. We have a newer report of the same issue in #10330 that may give us more info.