how to fix 0x0000138A on Visual Studio Community and Enterprise

BumpyJumpy12 0 Reputation points
2026-11-15T00:58:36.2433333+00:00

I was trying to install Visual Studio 2026 Enterprise from my.visualstudio.com, but every time I tried to install it, it kept crashing after the end, even with administrator privileges. After that, I tried to install Visual Studio Community from the Microsoft Store, but that showed me error 0x0000138A. I checked the Microsoft Learn page about it, but that was no help.

Developer technologies | Visual Studio | Setup
0 comments No comments

3 answers

Sort by: Most helpful
  1. Brian Pham (WICLOUD CORPORATION) 1,430 Reputation points Microsoft External Staff Moderator
    2026-11-16T03:58:27.2233333+00:00

    Hi @BumpyJumpy12 ,

    Thanks for posting. Error 0x0000138A is 5002 in decimal. That looks like an exit code from the Visual Studio Installer, not a Windows or Microsoft Store error. The Store version of Visual Studio Community uses the same installer as the Enterprise version, so both failures probably have the same cause.

    1. When you say the Enterprise install "crashed after the end", does the installer close or show an error during the final step, or does the install finish and Visual Studio crash when you open it?
    2. Can you try too open Visual Studio Installer and let me know whether Visual Studio 2026 is listed under Installed?

    Things you can try:

    1. Clear your temp folder and close overlay apps. Close any apps with overlays, such as Discord, Steam or Razer Synapse. Then press Win+R, type %TEMP%, and delete everything in that folder. Skip any files that are in use.
    2. Open Command Prompt as administrator and run "C:\Program Files (x86)\Microsoft Visual Studio\Installer\InstallCleanup.exe"
    3. Reinstall using the latest bootstrapper. Please don't use the Microsoft Store this time. Instead, download and run the bootstrapper for your edition:

    If the problem continues, please share the logs so I can see exactly which component is failing.

    • First restart Windows, then run the installer again until you see the same error or crash.
    • Right after it fails, before you retry or change anything, press Win+R, type %TEMP% and press Enter. Sort the folder by Date modified and find the newest log files that start with dd_bootstrapper, dd_client and dd_setup.

    The dd_setup_*_errors.log file is usually the most useful one. Please attach these files to your reply here.

    If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.

    Thank you.

    Was this answer helpful?

    0 comments No comments

  2. Rukshan edirisinghe 2,770 Reputation points
    2026-11-15T04:12:17.7733333+00:00

    Hi @BumpyJumpy12

    Since both the Enterprise installer and the Store version fail, the Visual Studio Installer on your PC was most likely left half-finished by the first crash. The Store version uses the same installer underneath, so it trips over the same broken state. Clearing it out and starting fresh usually gets past this:

    1. Close the Visual Studio Installer and the Microsoft Store.
    2. Open Command Prompt as administrator and run "C:\Program Files (x86)\Microsoft Visual Studio\Installer\InstallCleanup.exe" -f (skip this step if the file isn't there).
    3. Restart Windows.
    4. Download the installer from my.visualstudio.com again, right-click it and choose Run as administrator.
    5. Pick just one workload for the first install, then add the rest once that finishes.

    If it still crashes near the end, the setup logs in %TEMP% (files starting with dd_) will show which package fails.

    If it fails again, could you share the last few lines of the newest dd_setup log?

    If my response resolved your issue, please consider accepting it as the answer. If the issue persists, let me know and I'll be happy to continue helping.

    Reference:

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-11-15T00:59:30.72+00:00

    Remove any trailing semicolon from the Windows TEMP and TMP environment variables, restart Windows, and then rerun the Visual Studio 2026 installer; this is the closest documented match for error 0x0000138A affecting Visual Studio setup.^1^

    Correct TEMP and TMP

    1. Close the Microsoft Store and Visual Studio Installer.
    2. Press Win+R, enter sysdm.cpl, and press Enter.
    3. Select Advanced → Environment Variables.
    4. Under both User variables and System variables, inspect TEMP and TMP.
    5. Remove a trailing semicolon if present:
      • Incorrect: %USERPROFILE%\AppData\Local\Temp;
      • Correct: %USERPROFILE%\AppData\Local\Temp
      • A typical system value is C:\Windows\Temp
    6. Confirm that each referenced directory exists, is writable, and has adequate free space. An invalid, read-only, or full temporary directory can prevent creation of required files.^2^
    7. Select OK in every dialog and restart Windows.
    8. Retry the Enterprise bootstrapper downloaded from my.visualstudio.com. If needed, retry Community afterward; administrator elevation has already been tested and does not need to be repeated as a separate fix.

    You can inspect the effective values before changing them:

    "User TEMP:    $([Environment]::GetEnvironmentVariable('TEMP','User'))"
    "User TMP:     $([Environment]::GetEnvironmentVariable('TMP','User'))"
    "System TEMP:  $([Environment]::GetEnvironmentVariable('TEMP','Machine'))"
    "System TMP:   $([Environment]::GetEnvironmentVariable('TMP','Machine'))"
    "Process TEMP: $env:TEMP"
    "Process TMP:  $env:TMP"
    

    If an incomplete Visual Studio instance remains

    Open Start → Visual Studio Installer. If Enterprise or Community appears under Installed, select More → Repair. Repair reacquires damaged installation payloads, but it also resets the Visual Studio environment and removes some local customizations.^3^

    The Repair option is available only for installed instances. Skip this step if the edition appears only under Available or is not listed.

    If 0x0000138A continues

    That hexadecimal value is not listed among the documented Visual Studio command-line installer result codes, so the setup logs are needed to identify which component actually failed. Visual Studio writes logs under %TEMP%; sort that directory by date and examine files beginning with:

    • dd_bootstrapper
    • dd_client
    • dd_setup

    These correspond to the bootstrapper, installer application, and setup engine.^4^

    For a complete diagnostic package:

    1. Download the Microsoft Visual Studio and .NET Framework log collection tool.
    2. Open an elevated Command Prompt under the same Windows account used for the failed installation.
    3. Run Collect.exe.
    4. Retrieve %TEMP%\vslogs.zip.
    5. Open Visual Studio Installer → feedback icon → Report a problem and attach the failure details. The installer can also attach its latest setup log automatically.^5^

    Last resort: remove failed setup state

    Use InstallCleanup.exe only if repair or normal uninstallation fails. It can remove shared features used by other Visual Studio installations or products.^6^

    1. Close Visual Studio Installer.
    2. Back up any required Visual Studio settings.
    3. Open an administrator Command Prompt.
    4. Run the cleanup tool with the documented -i option for the version being reinstalled:
    "C:\Program Files (x86)\Microsoft Visual Studio\Installer\InstallCleanup.exe" -i [version]
    
    1. Restart Windows and rerun a newly downloaded Visual Studio bootstrapper.

    Avoid -f when the intention is to reinstall: that option removes additional shared features and is intended for removing Visual Studio without reinstalling it.


    References

    1. problême de téléchargement - Microsoft Q&A
    2. Can't create necessary temporary file
    3. Repair your Visual Studio installation | Microsoft Learn
    4. Use command-line parameters to install, update, and manage Visual Studio
    5. Troubleshoot Visual Studio installation and upgrade issues
    6. Uninstall or remove Visual Studio
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.