Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

6 Troubleshooting

nanonestor edited this page Jan 20, 2026 · 3 revisions

Still having trouble even after reading the below troubleshooting and trying solutions? Join the Discord home for the project here for support:

Download Latest Version


Troubleshooting


CMD / Command Prompt not working correctly

You see the message in the image below:

CMD broken

This message means the script detected that basic command functions for your Windows CMD are not functioning correctly. Either Windows is not configured correctly or some program has broken it's function.

(追記) Two repair solutions are recommended: (追記ここまで)

  1. (追記) Use Windows System File Checker tool (追記ここまで) (SFC) as described here by Microsoft.

    • Open a Windows command prompt (press the Windows key or click Windows search, and then search 'cmd'.
    • Click the option to 'run as administrator' OR right click the option and click 'run as administrator'.
    • First enter the command:
      DISM.exe /Online /Cleanup-image /Restorehealth
      Wait for the tool to finish.
    • Next enter the command:
      SFC /scannow
      Wait for the tool to finish.
    • It's recommended to restart your computer to let any system updates / changes take effect.
    • Try running the Universalator.bat file again.
  2. (追記) Manually add the Windows commands location to your system PATH environmental variable. (追記ここまで)
    As described here

    • Windows search the word 'environ' and select the item found named Edit the system environment variables.

    • Once at this window click the Envornment variables button.

    • In the box named System Variables select the entry named (exactly) Path (or PATH) and then click the Edit button below.

    • Look at the following list of folder locations (below). All of them should be items inside System Path.
      If any of them are not present as entries: Click the new button and add, one at a time, each of the missing entries.

      (You can highlight and copy/paste the text lines below if you want).

      C:\Windows\SysWOW64
      C:\Windows\System32
      C:\Windows\System32\Wbem
      C:\Windows\System32\WindowsPowerShell\v1.0\
      
    • Click 'OK' on the windows for this 'edit' window, 'OK' for the 'Environment Variables' window, and 'OK' for the 'System Properties' window. You must click OK on all 3 of these windows or else changes will not apply!

    • Restart your computer.

    • Try running the Universalator.bat file again.


No Window opens when trying to run the Universalator.bat script file.

First - Check to see if command windows will open at all for you by searching windows for CMD and clicking to open item 'Command Prompt'.

  • Try the same repair procedures as troubleshooting for CMD / Command Prompt not working correctly except:

    • If attempting the System File Checker tool (SFC) repair procedure:
      Instead of opening a CMD / Command window, try and open a powershell window to enter the same commannds.
      Windows search the word 'powershell', right click the Powershell item, and select 'run as adminstrator'.
  • If the repair procedures mentioned above fail - it's possible you have a CMD hook keeping your command prompt from working correctly. Options:

    • Visit the Universalator home discord for support. (link above)
    • Seek additional tools to remedy it.
    • Reinstall Windows.

Clone this wiki locally

AltStyle によって変換されたページ (->オリジナル) /