how to use 'new' application compatibility troubleshooter?

Question

I am trying to troubleshoot a steam game i have had for a number of years, but have not run in a really long time. The title is "Shoot Many Robots". The game opens then closes without doing or displaying anything. windows event viewer is reporting a '0xc0000005' error when I try to run the game. (see error below). The error seems to be coming from the game itself, and it is the only thing currently on my system not able to run normally. Running the windows compatibility troubleshooter only makes sense at this stage, however the new version based off of the get help app, does not seem to be able to work. I followed ALL the instructions, form the Microsoft support pages, the get help app, and from windows itself. but the new version seems to send you into an endless loop. The 'get help' based troubleshooter seems to be only able to troubleshoot apps if it appears on the detected list it generates. if the app is not listed, then you are unable to troubleshoot the intended program, even if you right click on the .exe and select troubleshoot compatibility or selecting 'run compatibility troubleshooter' from the .exe properties (right click > properties). how do I use the 'new' troubleshooter to troubleshoot my game on windows 11 Pro 25h2?

Faulting application name: ShootManyRobots.exe, version: 1.1.1.30747, time stamp: 0x4f845189 Faulting module name: ShootManyRobots.exe, version: 1.1.1.30747, time stamp: 0x4f845189 Exception code: 0xc0000005 Fault offset: 0x00895311 Faulting process id: 0xBB80 Faulting application start time: 0x1DC3C50BC6E71BC Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe Report Id: 5e99017e-920b-4acc-ba43-ce53aaa1578c Faulting package full name: Faulting package-relative application ID:

Log Name: Application Source: Application Error Date: 10/13/2025 7:50:38 AM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords:
User: MSI\Cybot Computer: MSI Description: Faulting application name: ShootManyRobots.exe, version: 1.1.1.30747, time stamp: 0x4f845189 Faulting module name: ShootManyRobots.exe, version: 1.1.1.30747, time stamp: 0x4f845189 Exception code: 0xc0000005 Fault offset: 0x00895311 Faulting process id: 0xBB80 Faulting application start time: 0x1DC3C50BC6E71BC Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe Report Id: 5e99017e-920b-4acc-ba43-ce53aaa1578c Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-10-13T14:50:38.7326826Z" /> <EventRecordID>6081</EventRecordID> <Correlation /> <Execution ProcessID="27072" ThreadID="62396" /> <Channel>Application</Channel> <Computer>MSI</Computer> <Security UserID="S-1-5-21-134317040-2025772203-3950351876-1001" /> </System> <EventData> <Data Name="AppName">ShootManyRobots.exe</Data> <Data Name="AppVersion">1.1.1.30747</Data> <Data Name="AppTimeStamp">4f845189</Data> <Data Name="ModuleName">ShootManyRobots.exe</Data> <Data Name="ModuleVersion">1.1.1.30747</Data> <Data Name="ModuleTimeStamp">4f845189</Data> <Data Name="ExceptionCode">c0000005</Data> <Data Name="FaultingOffset">00895311</Data> <Data Name="ProcessId">0xbb80</Data> <Data Name="ProcessCreationTime">0x1dc3c50bc6e71bc</Data> <Data Name="AppPath">C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe</Data> <Data Name="ModulePath">C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries\ShootManyRobots.exe</Data> <Data Name="IntegratorReportId">5e99017e-920b-4acc-ba43-ce53aaa1578c</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event>

Answer 1

issus was NOT resolved. the descision for the changes in the program compatibility troubleshooter seem to made in poor judgement. especially when at the end of trying to troubleshooot, 'get-help' displays the following - Please follow the following steps:1. Select Start button

2. Type File Explorer and select the option
3. Navigate to the .exe file
4. Right click on the .exe file and select Show more options
5. Select Troubleshoot compatibility

these steps seem to no longer be accurate, since it just sends you into an endless loop trying to troubleshoot the program.

if you have further guidance, i am willing to try it. i have already tried having steam verify my game files, uninstalling the game and having steam redownload it. i also tried moving the games files over to my SSD (C:) using steam's built in tool. after setting the compatibility settings suggested by you, windows does in fact asked if the program worked correctly, but again, answering 'NO', just sends you down the rabbit hole once more.

Answer 2

Hi Chris,

You are not doing anything wrong. On Windows 11 25H2 the old MSDT-based Program Compatibility Troubleshooter was retired and replaced by a Get Help flow. Today that flow only targets apps it detects in its inventory. There is no supported way to point it at an arbitrary .exe that does not appear in the list, so you cannot force the new troubleshooter to run against ShootManyRobots.exe. This is a design change, not a bug in your PC.

Try this instead. Close Steam, open C:\Program Files (x86)\Steam\steamapps\common\Shoot Many Robots\ShootManyRobots\Binaries, right-click ShootManyRobots.exe and choose Properties. Open the Compatibility tab. Turn on Run this program in compatibility mode for and select Windows 7. Turn on Disable fullscreen optimizations. Click Change high DPI settings, turn on Override high DPI scaling behavior, set the drop down to Application, then click OK.

Back on the Compatibility tab, also turn on Run this program as an administrator. Click Apply and OK. Now launch the game once directly from ShootManyRobots.exe, then try from Steam. If the 0xc0000005 access violation was caused by modern display handling, DPI, or privilege changes, these per app shims typically let the title start even though the new troubleshooter cannot be targeted.

If it still crashes, tell me and I will give you the next step.

Answer 3

Hey, I have a similar issue with F1 2010 by CodeMasters, purchased via Steam.

I go to the exe and run the troubleshooter and end up in a loop. Not being able to point the troubleshooter to a specific program is untenable. I can play DOOM (1993), the first Borderlands (2006), and other similar old games and they run just fine, WHY does THIS game freak windows out? Whatever this windows 11 setting is, we need to be able to adjust it or at least tell the troubleshooter which programs we want to use. I now have a game that I paid good money for, and I cannot use due to M$ brilliant ideas and ham fisted ways of executing said ideas. Don't go the way of google by taking adjustability away from users.

Answer 4

Accidental comment - plz delere

Answer 5

I ended up finding an.... 'Archived' copy of the game that some one had uploaded to archive.org. oddly that copy of the game worked flawlessly. I copied the files over my steam install for a test, and everything worked like it should, but as soon as i told steam to verify the files, it stopped working. It is my opinion that somehow, the files residing on the steam file servers got somehow corrupted and were never fixed with good copies. I did do a file comparison between the executables of the downloaded copy and my paid for, licensed copy of the game, and the only difference was that it seemed to be a slightly older version that what was listed on steamdb. So I suppose the compatibility troubleshooter would not have helped even if we were able to use the msdt version of the troubleshooter.