search

Foulest / RepairKit

All-in-one Java-based Windows repair and maintenance toolkit.
GNU General Public License v3.0
44 stars 2 forks source link

Can't start program #8

Closed tgillian closed 3 months ago

tgillian commented 3 months ago

Before you submit this issue, please make sure you have done the following:

Describe the bug When I click on the program Windows asks if I want to allow this app from an unknown publisher to make changes to this computer. I click on yes. The screen gives the busy blue circle on screen and then it just goes away.

Expected behavior I expected the program to start.

Actual behavior Nothing! It just goes away

To Reproduce Steps to reproduce the behavior:

  1. Go to c:\temp\repairkit
  2. Click on RepairKit-1.0.6.exe
  3. Windows asks if I want to allow program to make changes to my computer I say yes
  4. Nothing

Screenshots If applicable, add screenshots or animated GIFs to help explain your problem.

Additional context Have a Dell G7 15 Laptop. Running Microsoft Windows 11 Professional Workstation (x64) Build 22635.3720

Foulest commented 3 months ago

It's because you were running it from the %temp%\RepairKit directory. Fixed in the latest version @tgillian.

tgillian commented 3 months ago

Well, I must admit I am not the most talented in the computer field. However, a couple of comments. First, the temp file I was using was not the system temp file (%temp%) but a folder I created on the C: drive. Second, I downloaded the version 1.0.7. I have tried to run it from my NAS drive, a USB drive (which is where I probably would usually run it from, and a c:\Repairkit-1.0.7 folder. They all start to run it and then just go away. No errors, no messages, nothing. Guess I was not meant to use/look at your program.

Thanks for the answer though! I appreciate it.

Foulest commented 3 months ago

I can't replicate your error when starting RepairKit from the C:\RepairKit-1.0.7 directory or running it from a USB drive. The temp directory was a legitimate problem; it is fixed even though it wasn't the cause of your problem.

I've released a new version of RepairKit that outputs a RepairKit.log file used for debugging in the %temp% directory. Run it and attach it to this issue thread when you can.

tgillian commented 3 months ago

No change attached is the log. Hope it means something to you. I looked at the log and nothing jumped out at me. But, I don't know what the program does. RepairKit.log

I'm interested in what happened. Thanks for the help!

Foulest commented 3 months ago

Interesting. It just.. ends before it can draw the GUI at all.

Here, run this newly compiled version attached and post the log file. Let's see if we can get more information.

I suspect it has something to do with Intel UHD Graphics, but I'm not sure.

tgillian commented 3 months ago

Well, I ran it just as you wanted. Ran it from D:\RepairKit-1.0.8. Ran it as Admin. Sorry, no change. Just terminated in the log. Find the log attached. RepairKit.log

Foulest commented 3 months ago

Well... Clearly, some exceptions are being thrown but not caught. Interestingly, your log file is missing the security software section. Let's try something to guarantee that we catch whatever is happening absolutely.

Download and extract this newly compiled zip file and run the start.bat file. Absolutely everything should be logged and displayed in the console window.

tgillian commented 3 months ago

Sorry, no change. Did echo all in command console.

RepairKit.log

Foulest commented 3 months ago

Can you copy and paste the command console output into a log/txt file?

tgillian commented 3 months ago

Yep, in two files. (snippet). PGN files.

Screenshot 2024-06-16 120712 Screenshot 2024-06-16 120745

Foulest commented 3 months ago

Bingo. There's the problem. Okay. Fixing now.

Foulest commented 3 months ago

Should be fixed. For peace of mind, let's do the same thing again. Run this newly compiled build from the start.bat file after extracting it and send screenshots of the console.

tgillian commented 3 months ago

Touchdown! Don't know what you did but it works. What was the problem?

Thanks for your patience and assistance!

Foulest commented 3 months ago

For some reason, your system required missing accessibility features that no other system has needed when creating the GUI. I'm not sure if you have any accessibility settings enabled, but it tried to load something in the accessibility package that was not found. I've since added it. This was a whirlwind of an issue. Thank you for your patience as well! Shipping an update right now.