starred/Quasar

Fork 0

mirror of https://github.com/quasar/Quasar.git synced 2026-04-25 15:25:59 +03:00

[GH-ISSUE #20] Corrupted File Message #12

New issue

Closed

opened 2026-02-27 15:48:16 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 15:48:16 +03:00

Owner

Originally created by @yankejustin on GitHub (Mar 17, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/20

Issue where, when the client closes unexpectedly - often either shutting down the machine or closing via the server's command - the client cannot open the issue due to a Windows message popping up that states that there are 4 corrupted files in "C:\UsersMyUserName\Documents". Screenshot will be posted soon.

Originally created by @yankejustin on GitHub (Mar 17, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/20 Issue where, when the client closes unexpectedly - often either shutting down the machine or closing via the server's command - the client cannot open the issue due to a Windows message popping up that states that there are 4 corrupted files in "C:\Users*MyUserName*\Documents". Screenshot will be posted soon.

kerem

2026-02-27 15:48:16 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@MaxXor commented on GitHub (Mar 17, 2015):

Can you tell me which options you have used while building your client?

This window with the corrupted files comes from the Admin elevation trick.

@MaxXor commented on GitHub (Mar 17, 2015): Can you tell me which options you have used while building your client? This window with the corrupted files comes from the Admin elevation trick.

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@yankejustin commented on GitHub (Mar 17, 2015):

Options used to build client:
IP/Hostname: My IP
Port:4782
Password: 1234
Reconnect Delay: 5000 ms
Mutex: SjIIz4NsyJLQyHUBhUkGOwN88PRjFvHS
Install Client: FALSE
Enable Admin Elevation: TRUE
Change Icon: FALSE

However, even when I close the open client and rebuild everything, and even if I do NOT have "Enable Admin Elevation" checked when I build a new client and run it, the message will persist.
How should I find the corrupted files?

@yankejustin commented on GitHub (Mar 17, 2015): Options used to build client: IP/Hostname: My IP Port:4782 Password: 1234 Reconnect Delay: 5000 ms Mutex: SjIIz4NsyJLQyHUBhUkGOwN88PRjFvHS Install Client: FALSE Enable Admin Elevation: TRUE Change Icon: FALSE However, even when I close the open client and rebuild everything, and even if I do NOT have "Enable Admin Elevation" checked when I build a new client and run it, the message will persist. How should I find the corrupted files?

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@MaxXor commented on GitHub (Mar 17, 2015):

Delete all stuff from the old client first (be sure to kill the process), then rebuild it with Admin Elevation set to false. Please read this: https://github.com/MaxXor/xRAT#compiling

@MaxXor commented on GitHub (Mar 17, 2015): Delete all stuff from the old client first (be sure to kill the process), then rebuild it with Admin Elevation set to `false`. Please read this: https://github.com/MaxXor/xRAT#compiling

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@yankejustin commented on GitHub (Mar 17, 2015):

I dug a bit deeper and realized that I had forgotten to delete a few hanging files. I will see if it works very soon. I will test if it works as it did yesterday on my main machine and I will report the results as soon as I can.

@yankejustin commented on GitHub (Mar 17, 2015): I dug a bit deeper and realized that I had forgotten to delete a few hanging files. I will see if it works very soon. I will test if it works as it did yesterday on my main machine and I will report the results as soon as I can.

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@yankejustin commented on GitHub (Mar 17, 2015):

As for now, the client is no longer causing Windows to bark at me about corrupted files. :)

@yankejustin commented on GitHub (Mar 17, 2015): As for now, the client is no longer causing Windows to bark at me about corrupted files. :)

kerem commented

2026-02-27 15:48:17 +03:00

Author

Owner

@MaxXor commented on GitHub (Mar 17, 2015):

Alright, good to know it's working for you!

@MaxXor commented on GitHub (Mar 17, 2015): Alright, good to know it's working for you!

kerem referenced this issue

2026-02-27 15:52:56 +03:00

[PR #228] [MERGED] Remote desktop fix #1055