Windows Games Asking For Emulator

[Hades68]

I had hundreds of Windows games imported into Launchbox as shortcuts which were working just fine.  I had to remove them all and re-add them, but now when I try to launch them it keeps asking me to configure an emulator for them, even though I imported them as Windows games.

Any ideas?

[Hades68]

I found the solution!

For some reason when I re-imported the Windows games, the "Use an emulator to play this game (primarily for console games)" option was ticked on the Emulation tab of the Edit Metadata/Media... window.  I have no idea why this was ticked by default for Windows games.

However, it can't be unticked in the bulk metadata change option, so I had to edit the \LaunchBox\Data\Platforms\Windows.xml file and do a find and replace on "<Emulator>00000000-0000-0000-0000-000000000000</Emulator>" replacing it with "<Emulator />".

Now my Windows games all launch again!

[ElDiablo77]

I had the same issue. I tried doing as described, I replaced the whole line with <Emulator /> yet it's still not launching games. Instead I renamed the Windows.xml after removing all the shortcuts and letting Launchbox generate a new Windows.xml file. I then re-added the shortcuts and everything works as it should.

Thanks for posting the solution as too many times people just say "never mind I've fixed it"

[AstroBob]

Hi Folks,

Thanks for reporting this, this is a known issue in 13.18 as the Use Emulator to paly this game is incorrectly being checked when doing these types of imports. I just wanted to let you know that we’ve confirmed this behavior, and it is indeed a bug. We’re working to address this in our upcoming beta.

In the meantime, for storefront games, it’s recommended to use storefront importers. For standalone .exe files, you can simply uncheck the Use emulator to play this game option after importing.

I understand this is far from an ideal solution in the short-term, and I sincerely apologize for the inconvenience caused. I’ll keep you updated as soon as the fix is available.

Cheers,

[BDeRbDaMaStA]

Hello AstroBob,

Any updates to this issue? It looks like this bug followed into 13.19 as well. 

[spiritedusual]

On 2/14/2025 at 4:14 AM, BDeRbDaMaStA said:

Hello AstroBob,

Any updates to this issue? It looks like this bug followed into 13.19 as well. 

Second

[AstroBob]

Hi Folks,

Thanks for the report, however, this should have been addressed in 13.19. The fix was:
 

Quote

Fixed: Corrected an error introduced in version 13.18 where dragging and dropping non-ROM game files would incorrectly assign an unassigned emulator value

I've just given this another test and it appears to be working, here's what I'm doing:

• Take a .exe file and drag/drop it onto LaunchBox
• When asked what type of game files are you importing, I select None of the above
• Follow the wizard to import the game

The resulting import shout NOT have the Use emulator to play this game check under Launching > Emulator

Please let me know if you're import games differently that produce a different result where this option is still remaining checked

[Hades68]

I can confirm that this is not fixed in the latest version 13.19, since I don't drop the .exe file into Launchbox, instead I keep shortcuts for all of my games in a single folder (including Steam url shortcuts) and then I choose Tools > Scan > For Added Windows ROMS... which then detects any shortcuts I've added to the folder.

Unfortunately when I do this the Use emulator to play this game option is still ticked under Launching > Emulator

An additional issue I have found is that when I delete any of the shortcuts from the folder, then do Tools > Scan > For Removed Windows ROMS... Launchbox does not detect that the shortcuts have gone so it claims no Windows games have been removed, which means I have to remove them from Launchbox manually.

[AstroBob]

Thanks for the update!

The bug fix in 13.19 specifically addressed users who were dragging and dropping shortcuts into the LaunchBox interface and following the wizard that specified applications, that were being incorrectly set as ROMs. However, based on how you’re currently handling this, it turns out this behaviour is actually expected.

The Scan for Added ROMs function, as the name suggests, is designed specifically for ROM files, which is why anything detected during this process ends up with the Use Emulator checkbox enabled. That said, I totally get why this feels counterintuitive—especially for platforms like Windows, where applications aren’t traditional ROMs. At its core, the function simply doesn’t have a way to distinguish between a ROM and an application, which is why it’s treating them the same way.

I’m curious about your workflow—what’s the reason for relying on shortcuts rather than using the storefront importers? I can understand if it’s for non-storefront games that might be installed in different locations, but you also mentioned Steam games are included. Just wondering if there’s a specific use case we’re not currently accommodating that we could improve.

You also mentioned that this “used to work.” I checked back to 13.17 (since the initial report was for 13.18), but even in that version, it looks like shortcuts weren’t being recognized correctly at all.

I definitely think there’s room for improvement when it comes to Windows imports and a better way to handle non-storefront games. If you can share a bit more about your specific setup, I’d love to scope out a possible feature improvement and get it logged for you.

Looking forward to hearing your thoughts!

[spiritedusual]

3 hours ago, AstroBob said:

Thanks for the update!

The bug fix in 13.19 specifically addressed users who were dragging and dropping shortcuts into the LaunchBox interface and following the wizard that specified applications, that were being incorrectly set as ROMs. However, based on how you’re currently handling this, it turns out this behaviour is actually expected.

The Scan for Added ROMs function, as the name suggests, is designed specifically for ROM files, which is why anything detected during this process ends up with the Use Emulator checkbox enabled. That said, I totally get why this feels counterintuitive—especially for platforms like Windows, where applications aren’t traditional ROMs. At its core, the function simply doesn’t have a way to distinguish between a ROM and an application, which is why it’s treating them the same way.

I’m curious about your workflow—what’s the reason for relying on shortcuts rather than using the storefront importers? I can understand if it’s for non-storefront games that might be installed in different locations, but you also mentioned Steam games are included. Just wondering if there’s a specific use case we’re not currently accommodating that we could improve.

You also mentioned that this “used to work.” I checked back to 13.17 (since the initial report was for 13.18), but even in that version, it looks like shortcuts weren’t being recognized correctly at all.

I definitely think there’s room for improvement when it comes to Windows imports and a better way to handle non-storefront games. If you can share a bit more about your specific setup, I’d love to scope out a possible feature improvement and get it logged for you.

Looking forward to hearing your thoughts!

This is great if you are only trying to add one game via drag and drop.

If you want to add multiple games at once, drag and drop is slow. Previously, "importing rom" was the way to go. Yes it says ROM, but like previously mentioned when adding 100pc games at once drag and drop is just not the way to go.

[Hades68]

5 hours ago, AstroBob said:

Thanks for the update!

The bug fix in 13.19 specifically addressed users who were dragging and dropping shortcuts into the LaunchBox interface and following the wizard that specified applications, that were being incorrectly set as ROMs. However, based on how you’re currently handling this, it turns out this behaviour is actually expected.

The Scan for Added ROMs function, as the name suggests, is designed specifically for ROM files, which is why anything detected during this process ends up with the Use Emulator checkbox enabled. That said, I totally get why this feels counterintuitive—especially for platforms like Windows, where applications aren’t traditional ROMs. At its core, the function simply doesn’t have a way to distinguish between a ROM and an application, which is why it’s treating them the same way.

I’m curious about your workflow—what’s the reason for relying on shortcuts rather than using the storefront importers? I can understand if it’s for non-storefront games that might be installed in different locations, but you also mentioned Steam games are included. Just wondering if there’s a specific use case we’re not currently accommodating that we could improve.

You also mentioned that this “used to work.” I checked back to 13.17 (since the initial report was for 13.18), but even in that version, it looks like shortcuts weren’t being recognized correctly at all.

I definitely think there’s room for improvement when it comes to Windows imports and a better way to handle non-storefront games. If you can share a bit more about your specific setup, I’d love to scope out a possible feature improvement and get it logged for you.

Looking forward to hearing your thoughts!

Thanks for your rapid response!

I rely on shortcuts because when I install Windows games I don't have them create an entry in the Start menu. I also have some indie games which don't appear in the Start menu, and I don't have a Steam API key which is needed to use the Steam import option.

My workflow is as follows:

When I initially import my Windows games into Launchbox, I use the Wizard from Tools > Import > ROM files > Single Platform, then add my shortcuts folder, at What platform are you importing games for? I select Windows from the list, at What emulator would you like to use? I leave that field blank, at Would you like to move or copy the files? I select Use the files in their current location, at Would you like to download metadata for your games? I leave that ticked, on the next three screens I select the metadata I want and set any custom options, then Launchbox lists the shortcuts it found in the folders and I click Finish.

After this, if I add any new shortcuts to the folder, that is when I use the Scan for Added ROMs option.

Wouldn't it be possible to flag the games as Windows instead of ROMs when Windows is selected as the platform and the emulator field is left blank in the import wizard, and not set the use emulator flag?

Edited February 19 by Hades68

[AstroBob]

Thanks for the additional context! You both make some great points, and the fact is that the Scan for Added ROMs functionality wasn’t originally intended for Windows shortcuts, so there’s definitely room for improvement in this area.

I’ve gone ahead and scoped out a proper feature request based on your feedback. You can view and upvote it here:

🔗 https://feedback.launchbox.gg/p/support-for-windows-shortcuts-in-scan-for-added-roms

Thanks for bringing this to our attention! While I wasn’t able to confirm that this behavior has changed in recent versions (as far as I know, it’s always been this way), I believe these reports may have been mixed up with the drag-and-drop issue in LaunchBox, which was an actual bug that has since been fixed.

However, if you’re certain it behaved differently in a previous version, please let me know which version that was, and I’ll do my best to track it down.

[spiritedusual]

8 hours ago, AstroBob said:

Thanks for the additional context! You both make some great points, and the fact is that the Scan for Added ROMs functionality wasn’t originally intended for Windows shortcuts, so there’s definitely room for improvement in this area.

I’ve gone ahead and scoped out a proper feature request based on your feedback. You can view and upvote it here:

🔗 https://feedback.launchbox.gg/p/support-for-windows-shortcuts-in-scan-for-added-roms

Thanks for bringing this to our attention! While I wasn’t able to confirm that this behavior has changed in recent versions (as far as I know, it’s always been this way), I believe these reports may have been mixed up with the drag-and-drop issue in LaunchBox, which was an actual bug that has since been fixed.

However, if you’re certain it behaved differently in a previous version, please let me know which version that was, and I’ll do my best to track it down.

I cant say what version I only know that after I added GZDOOm as an emulator it started popping all the time.

I did just figure a workaround that worked for me though. I changed the associated platform for GZDOOM to be some random platform and the option is now blank when importing from the tools>import. Not perfect but it works.

[Hades68]

Thanks for all of your help, AstroBob!

One more thing on this Windows games topic; when I delete Windows shortcuts from the folder then do Tools > Scan > For Removed Windows ROMS... Launchbox doesn't detect that the shortcuts have been removed and ask me to delete the games.

[AstroBob]

15 hours ago, Hades68 said:

Thanks for all of your help, AstroBob!

One more thing on this Windows games topic; when I delete Windows shortcuts from the folder then do Tools > Scan > For Removed Windows ROMS... Launchbox doesn't detect that the shortcuts have been removed and ask me to delete the games.

I wouldn't be surprised if it's not treating those shortcuts as game files, hence why it isn't picking anything up to be removed. I've added that to the scoped feature though, since you're right, it shouldn't just be able to scan for added shortcuts but remove them by running the scan for deleted ROMs as well

[Hades68]

That's great!  Thanks for this, AstroBob!