search

NiyaShy / XB1ControllerBatteryIndicator

A tray application that shows a battery indicator for an Xbox-ish controller and gives a notification when the battery level drops to (almost) empty.
GNU General Public License v2.0
710 stars 53 forks source link

Not executing after a Windows "repair". #74

Closed Frankaupolis closed 1 year ago

Frankaupolis commented 1 year ago

Hi, I've just made a "repair" of my Windows 10 using Microsoft's "Windows 10 installation media" creation tool. Since then only two issues have arisen, one of which is XB1ControllerBatteryIndicator not executing at all. I've tried running as admin but to no avail. I've tried both 1.2.1 and 1.3.1.1 versions. Anyone have an idea of what might be causing this?

Thanks in advance!

François

NiyaShy commented 1 year ago

Hey, that sounds... weird. Have you checked event viewer if it maybe silently crashes?

Other than that I currently can't think of that many things that could be wrong. Unless of course the "repair" messed up your windows installation more than is was before. Just in case, you could start a "cmd" window with admin permissions and run the command "sfc /scannow", that will scan your system for major inconsistencies and tries to fix them if any are found.

Frankaupolis commented 1 year ago

Hi NiyaShy, thanks for your response. "Have you checked event viewer..?": I'm not sure how to use this, I'm not at that level.. yet.. ;) All I can see is, right after I launch the application, I see the app in Task Manager for 1 to 2 seconds before it disappears. I did just run the "sfc /scannow" command and it did find and fixed some errors. I then rebooted, but to no avail. Still the same behavior. Thanks for your help though. I will post here if anything changes.

NiyaShy commented 1 year ago

Hey,

for event viewer, do a right click on the "windows flag" button of your task bar, you should have an entry for it at the top of the menu. In there, expand "windows protocols" and open the "Application" log. (My system is in German, so the entries might be called slightly different)

When it crashes, you typically get 2 entries in the application log: one marked as an error, and one marked as information with the source "AppCrash". The content of both those entries can help to narrow down what's wrong.