Risoluzione dei problemi

Risoluzione dei problemi di MuhRO

La maggior parte dei problemi può essere risolta senza reinstallare Windows o disattivare il software di sicurezza. Segui i passaggi seguenti nell'ordine e fermati quando il problema è risolto.

Prima di iniziare

1. Chiudi Muh.exe, Muh_Patcher.exe e updater.exe. Usa Gestione attività se uno rimane aperto.
2. Riavvia il computer se Windows, un driver grafico o un runtime sono stati aggiornati di recente.
3. Avvia Muh_Patcher.exe dalla cartella di gioco di MuhRO. Non avviare Muh.exe direttamente.
4. Lascia che il patcher completi l'aggiornamento prima di premere Play.
5. Apri Game Setup, seleziona le impostazioni grafiche e premi Save almeno una volta.
6. Se compare un errore, conserva il testo esatto o fai uno screenshot prima di chiuderlo.

Cartella di installazione consigliata

Installa o estrai MuhRO in una cartella locale con un percorso breve, ad esempio:

C:\Games\MuhRO

Evita di installare il gioco in:

• C:\Program Files o C:\Program Files (x86);
• le directory Windows o System32;
• Downloads, Desktop o Documents;
• OneDrive o un'altra cartella sincronizzata con il cloud;
• un'unità di rete;
• una cartella con lettere non inglesi, simboli speciali o un percorso insolitamente lungo.

Si consiglia un percorso che utilizzi solo normali lettere latine e numeri. Non eseguire il patcher dall'interno di un archivio ZIP; estrai prima il client completo.

Problemi con il client

Il client non si avvia, si chiude senza errori, segnala un errore DLL MSVCP/VCRUNTIME o va in crash in modo casuale

Prova questi passaggi:

1. Avvia il patcher e assicurati che tutti gli aggiornamenti vengano completati.
2. Esegui Game Setup, scegli una risoluzione normale e salva le impostazioni.
3. Installa entrambe le versioni correnti di Microsoft Visual C++ Redistributable:
   • Visual C++ x86
   • Visual C++ x64
4. Riavvia Windows dopo aver installato o riparato i runtime.
5. Chiudi temporaneamente i software che inseriscono overlay nei giochi, come overlay di registrazione, ReShade, RTSS o strumenti simili.
6. Aggiorna il driver grafico direttamente da Intel, AMD o NVIDIA.
7. Controlla Sicurezza di Windows o la Cronologia protezione dell'antivirus per i file rimossi dalla cartella MuhRO.

Il runtime Visual C++ x86 è richiesto dal client di gioco a 32 bit, anche su Windows a 64 bit. Non scaricare singoli file DLL da siti di download di DLL.

Errore vuoto all'avvio del client

Questo accade comunemente quando Muh.exe viene avviato direttamente. Avvia sempre Muh_Patcher.exe, accedi e lancia l'account di gioco selezionato tramite il patcher.

Le scorciatoie sul desktop devono puntare a Muh_Patcher.exe, non a Muh.exe.

“Cannot init D3D” o errore di inizializzazione grafica

Apri Game Setup nel patcher e prova quanto segue:

1. Seleziona DirectX 9 e salva le impostazioni.
2. Se DirectX 9 non funziona, prova DirectX 7.
3. Prova la modalità finestra con una risoluzione comune come 1280×720 o 1920×1080.
4. Seleziona la scheda grafica corretta, soprattutto sui portatili con grafica integrata e dedicata.
5. Evita risoluzioni più grandi del monitor o combinazioni di frequenza di aggiornamento non supportate.
6. Aggiorna il driver grafico e riavvia Windows.

Se il messaggio menziona un file DirectX legacy mancante come D3DX9, XInput o un file simile, installa il Microsoft DirectX End-User Runtime ufficiale.

Remote Desktop sessions and virtual machines may not provide the required graphics acceleration. Test the game directly on the computer.

“GRF file has problem” or a game-data verification error

1. Close the game and press Retry or restart the patcher.
2. Let the patcher finish verifying and repairing the installation.
3. Temporarily disable custom Addons or Gray Map modifications through the patcher and test again.
4. Check whether antivirus software removed a file.
5. Make sure sufficient free disk space is available.
6. If repair repeatedly fails, perform a clean reinstall into a new empty folder.

Do not randomly delete GRF files or copy GRFs from another server. The patcher can only safely repair files that belong to the current MuhRO release.

Game starts but displays incorrectly, flickers, is black, or has very low FPS

1. Save Game Setup again.
2. Switch between DirectX 9 and DirectX 7.
3. Test windowed mode and a lower resolution.
4. Make sure the intended GPU is selected.
5. Disable overlays and third-party graphics modifications.
6. Reset any Windows compatibility mode previously applied to Muh.exe.
7. Update the graphics driver.

Change one setting at a time so you can identify which change fixed the problem.

“Rejected from Server. (3)”

1. Close every running MuhRO client.
2. Start the patcher again and sign in with your Master Account e-mail address.
3. Select the intended Game Account in the patcher and launch it from there.
4. Do not enter the Master Account e-mail directly into the old in-game login screen.
5. If necessary, sign out of the patcher and sign in again to obtain a new launch session.

If the error continues, contact support with the game-account name and exact time of the attempt. Never send staff your password or security code.

Client freezes, disconnects or crashes after playing for a while

Before contacting support:

1. Test once without custom Addons, Gray Map modifications or overlay software.
2. Note the map, character action and exact local time when it happened.
3. Check whether the problem occurs on every character or only one character/map.
4. Run the fully patched default client from a clean installation folder.
5. Keep any crash message or automatic crash-report identifier shown by the client.

A single crash does not necessarily require reinstalling the client. Reinstall only after patching, graphics settings, runtimes and antivirus history have been checked.

Patcher issues

Help, I am using Linux

See How To Play on Linux.

Set up Wine and place the Linux patcher in the MuhRO game folder:

Muh Patcher for Linux

If Linux reports that the file is not executable, give it execute permission before starting it. Wine and Linux distributions differ, so include the distribution, Wine version and terminal error when requesting support.

Patcher does not start: incompatible software or architecture error

The default Windows patcher is 64-bit. A 32-bit Windows installation requires the 32-bit patcher:

Muh Patcher 32-bit

Save it as Muh_Patcher.exe inside the game folder. A 32-bit patcher is normally not needed on 64-bit Windows.

For Windows 7 64-bit, use the dedicated legacy version:

Muh Patcher for Windows 7 64-bit

Windows 7 and Windows 8.1 are obsolete operating systems and may no longer support every modern launcher component.

Patcher starts as a process but no window or update prompt appears

A patcher pinned directly to the Windows taskbar may hide its update prompt.

1. Open Task Manager and end every Muh_Patcher.exe and updater.exe process.
2. Start Muh_Patcher.exe directly from the game folder.
3. If a hidden update prompt may be active, press Enter once.
4. Remove the old pinned taskbar entry.
5. After the updated patcher starts successfully, create a normal desktop shortcut or pin the new executable again.

Patcher update fails, repeats the update prompt, or cannot replace itself

1. Close the game and all patcher/updater processes through Task Manager.
2. Start the patcher directly from the game folder rather than an old taskbar shortcut.
3. Verify that the game folder is writable and is not inside Program Files, Downloads or OneDrive.
4. Check antivirus Protection History.
5. Retry the update once.

If the automatic update still fails, download the correct patcher manually:

• Windows 64-bit, default
• Windows 32-bit
• Windows 7 64-bit
• Linux

Save the file into the game folder and replace the existing Muh_Patcher.exe. Make sure the browser did not save it under a name such as Muh_Patcher (1).exe.

Patcher opens but the page is blank or the embedded browser fails

The current patcher uses Microsoft Edge WebView2, not Internet Explorer.

1. Close all patcher processes.
2. Install or repair the Microsoft Edge WebView2 Runtime.
3. If the error says WebView2 is already installed, open %LOCALAPPDATA%\MuhRO\Patcher.
4. Rename the WebView2 folder to WebView2.old.
5. Start the patcher again. A fresh WebView2 profile will be created.

If this works, the renamed cache may be removed later. If it does not work, keep it until troubleshooting is complete.

Patching fails with an error in the bottom status bar

Copy or screenshot the complete bottom-bar message. The final part of the error is often the most useful part.

“Connection closed before message end” or another download error

1. Retry once.
2. Check the internet connection and make sure the computer's date and time are correct.
3. Temporarily disconnect from VPN or proxy software.
4. Do not repeatedly use Reset All Patches.
5. If the same file repeatedly fails, try a different network as a diagnostic test.
6. If patch data was reset and cannot be restored, download a fresh full client.

“Failed to get/take the update lock”

Another patcher process, folder permissions or an unsuitable installation path may prevent patching.

1. Close Muh.exe, Muh_Patcher.exe and updater.exe through Task Manager.
2. Restart Windows if the lock remains.
3. Move or reinstall MuhRO into a simple folder such as C:\Games\MuhRO.
4. Avoid spaces, special symbols, protected Windows folders and cloud-synchronized folders.

Running permanently as Administrator is not the preferred solution. A normal user-writable game folder is safer and avoids most permission problems.

MuhVault verification, manifest-signature, or signed-file error

1. Close the game and patcher completely.
2. Check antivirus Protection History for a file removed from the MuhRO folder.
3. Start the official patcher again and allow it to retry verification.
4. Do not delete GRFs, manifest files or signatures at random.
5. Do not download replacement DLL or GRF files from third-party websites.
6. If the same verification error remains, take a screenshot and perform a clean installation into a new folder.

Keep the old folder until the new installation works or staff has collected the required file information.

Security-code or login page error

1. Confirm that Windows date, time and time zone are set automatically.
2. Restart the patcher instead of refreshing the login repeatedly.
3. Disable VPN or proxy software temporarily.
4. Check that the firewall is not blocking Muh_Patcher.exe.
5. Install or repair Microsoft Edge WebView2 if the login page itself does not load.

Do not reset Internet Explorer; it is not used by the current patcher.

Antivirus and Windows Security

Security software may occasionally quarantine the patcher or a required game file because patchers download, verify and replace executable files.

A detection should not automatically be assumed to be harmless. Only restore a file when:

• MuhRO was downloaded from the official website or patcher;
• the detected path is inside the expected MuhRO installation;
• the filename matches the file reported missing by the patcher.

Restoring a MuhRO file from Microsoft Defender

1. Open Windows Security.
2. Select Virus & threat protection.
3. Open Protection history.
4. Select the MuhRO detection and verify its original path.
5. If you are confident it is the official MuhRO file, choose Restore or Allow on device.
6. Start Muh_Patcher.exe and retry patching so the installation is verified again.

If Defender removes the file again, an exception for the exact MuhRO folder may be required. Add only the specific game folder, not an entire drive or a broad folder such as C:\Games.

Do not disable antivirus or firewall protection completely.

Controlled Folder Access blocks the patcher

Windows Controlled Folder Access may block applications from modifying protected folders such as Desktop or Documents.

Moving MuhRO to C:\Games\MuhRO is normally preferable. Alternatively, allow the official Muh_Patcher.exe through Controlled Folder Access after checking its location.

Network and connection problems

1. Check the homepage or announcements for known maintenance.
2. Ensure Windows date and time are correct.
3. Restart the patcher and network connection.
4. Temporarily disable VPN or proxy software.
5. Allow the patcher through the firewall instead of disabling the firewall.
6. Try a different network or mobile hotspot only as a diagnostic test.
7. If one connection works and another does not, tell support which internet provider and country are affected.

Do not open router ports for MuhRO unless staff provides a specific documented reason.

Clean reinstall

Use a clean reinstall only after the simpler steps above have failed.

1. Close all MuhRO and patcher processes.
2. Rename the current folder to something such as MuhRO-old. Do not delete it yet.
3. Download the latest full client from the official MuhRO website.
4. Extract or install it into a new empty folder such as C:\Games\MuhRO.
5. Start the new patcher and let it finish completely.
6. Run Game Setup, save the settings and test the unmodified client.
7. Add custom maps or addons back one at a time only after the default client works.

Do not install a fresh client over a damaged or heavily modified old client. Keep screenshots and personal configuration files in the old folder until the new installation has been tested.

What not to do

• Do not start Muh.exe directly.
• Do not download missing DLL, EXE or GRF files from third-party file websites.
• Do not disable antivirus or firewall protection completely.
• Do not randomly delete GRFs, manifests, signatures or patch files.
• Do not combine files from different private servers.
• Do not repeatedly reset all patches unless instructed.
• Do not send anyone your password, security code or login token.

Information to provide when contacting staff

Please include:

• a screenshot and the complete error text;
• the exact date, local time and time zone when it happened;
• whether the problem occurs before patching, after pressing Play, during login or inside the game;
• Windows version and whether it is 32-bit or 64-bit;
• graphics-card model and driver version for graphics problems;
• patcher version from Properties → Details;
• the complete installation path;
• antivirus product and the relevant Protection History entry, if any;
• the troubleshooting steps already attempted;
• whether a new, clean installation reproduces the problem;
• the game-account name or character name when relevant.

Never include your password, security code or other private credentials.