[GH-ISSUE #767] Client now crashing after removing and replacing! #507

New issue

Closed

opened 2026-02-27 15:50:40 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 15:50:40 +03:00

Owner

Originally created by @ioxen on GitHub (May 14, 2019).
Original GitHub issue: https://github.com/quasar/Quasar/issues/767

I had Quasar 1.3 installed on my laptop (Windows 10 Home) aswell as another remote tool (dark comet) I decided to run malwarebytes to take them off quickly and replace Quasar with a new stub (I need to replace the hostname, as my old one did not connect)
Now, with every client I build and attempt to put on the laptop, the quasar client crashes. Specifically, I run the stub as an admin to put it on the computer. It shows immediately in Task manager with high usage, then within 3 seconds, crashes, with werfault.exe, cmd.exe and conhost.exe showing up when the quasar client dies. This repeats endlessly. It was working before, no issues (except the wrong hostname) until I ran malwarebytes (Ive long since uninstalled malwarebytes though) I just wanted to remove a couple programs quick, then replace one. Did I shoot my own foot? Will I have to re-install Win 10? Windows defender is very disabled and wasn't interfering before anyways. I would be very grateful for anyone's time on this.

To Reproduce
Not sure what to put here other then I have tried 6 times with all different settings in the client builder. I've tried installing it to App Folder, Program Files and System, I've tried changing the startup name, mutex, client tag, everything basically.

Expected behavior
Install quasar on laptop as before and have it start with windows

Screenshots
Sorry no real screenshots for this, just taskman showing the client for 3 seconds, crash, then it loops, as if trying to start, forever.

System

Server OS Windows 7 and Windows 10 (Tried both)
Client OS: Windows 10 Home
Quasar Version: 1.3.0, Commit-ID: 2564b2f

Additional context
I've searched for others having this issue on github, and found only 1 similar issue, the suggestion to fix it by downloading the latest stable version, did not fix it. That was the very same link I originally got quasar from off this site.
Recap: quasar worked, I ran malwarebytes, quasar was removed, I uninstalled malwarebytes, I built a new client and ran it on the cleaned laptop. Broke it.
I am very much in need of assistance from a learned expert.

Originally created by @ioxen on GitHub (May 14, 2019). Original GitHub issue: https://github.com/quasar/Quasar/issues/767 I had Quasar 1.3 installed on my laptop (Windows 10 Home) aswell as another remote tool (dark comet) I decided to run malwarebytes to take them off quickly and replace Quasar with a new stub (I need to replace the hostname, as my old one did not connect) Now, with every client I build and attempt to put on the laptop, the quasar client crashes. Specifically, I run the stub as an admin to put it on the computer. It shows immediately in Task manager with high usage, then within 3 seconds, crashes, with werfault.exe, cmd.exe and conhost.exe showing up when the quasar client dies. This repeats endlessly. It was working before, no issues (except the wrong hostname) until I ran malwarebytes (Ive long since uninstalled malwarebytes though) I just wanted to remove a couple programs quick, then replace one. Did I shoot my own foot? Will I have to re-install Win 10? Windows defender is very disabled and wasn't interfering before anyways. I would be very grateful for anyone's time on this. **To Reproduce** Not sure what to put here other then I have tried 6 times with all different settings in the client builder. I've tried installing it to App Folder, Program Files and System, I've tried changing the startup name, mutex, client tag, everything basically. **Expected behavior** Install quasar on laptop as before and have it start with windows **Screenshots** Sorry no real screenshots for this, just taskman showing the client for 3 seconds, crash, then it loops, as if trying to start, forever. **System** - Server OS Windows 7 and Windows 10 (Tried both) - Client OS: Windows 10 Home - Quasar Version: 1.3.0, Commit-ID: 2564b2f **Additional context** I've searched for others having this issue on github, and found only 1 similar issue, the suggestion to fix it by downloading the latest stable version, did not fix it. That was the very same link I originally got quasar from off this site. Recap: quasar worked, I ran malwarebytes, quasar was removed, I uninstalled malwarebytes, I built a new client and ran it on the cleaned laptop. Broke it. I am very much in need of assistance from a learned expert.