dussmannwurst

Thanks for the quick reply! Did that already, after the initial install Win11 prompted me to do that. So that doesn't fix it sadly

Hi guys, looking for same help here, as I have no clue what is going on. The thing is: I want to set up my LB collection on a Handheld device, additionally to my standard Home PC Install. Where I have zero issues btw, I'm running 13.18 on Win 10 there. Now I bought an Antec Device, which runs Win 11 Home 24H2. As soon as I started importing some Roms to that install of LB 13.18, I realized that RetroAchievements are not detected after scanning for them. I use the same Roms of course as I use on the PC install, where they show no problem. I manually tried to trigger the RAHasher.exe and the following error messages pop up in succession: The code execution cannot proceed because MSVCP140.dll was not found. Reinstalling the programm may fix this problem. The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the programm may fix this problem. I checked my Systems32 folder, and both dlls are there. Of course I did try to reinstall everything (LB, Runtimes, Redistributables), but to no avail. Would really appreciate any advice, clue or hint, as this is really bugging me. Thanks!

4,6k, so quite a difference I'd say...

Removed the creds and indeed it does not crash anymore when searching all platforms. Kudos for figuring that out. I will use that as a workaround for now. Thanks a lot!

I am, yes

I'm experiencing the exact same issue, and turned on the logging. Here it is: Hope this helps, I have no idea what could be causing out, the most dominant entry seems to be PM FIRST CHANCE EXCEPTION: My LB install is on a dedicated SSD, so performance has never been an issue...

Tried with Mupen64 next and F-Zero Expansion, and it works like a charm following https://www.libretro.com/index.php/mupen64plus-next-2-0-64dd-support-angrylion-and-gliden64-in-one-build-parallel-rsp-support-and-android/ The key seems to be grabbing the correct BIOS rom (the US retail one) and putting it named like this "IPL.n64" in the mupen64plus folder of retroarch/system. A quick google search for that exact name shall lead everyone to the correct file. Name your two roms like indicated on the page linked above F-Zero X (USA).z64 and F-Zero X (USA).z64.ndd and load the former. Heavy guitar riff upcoming 😉

Tried with Mupen64 next and F-Zero Expansion, and it works like a charm following https://www.libretro.com/index.php/mupen64plus-next-2-0-64dd-support-angrylion-and-gliden64-in-one-build-parallel-rsp-support-and-android/ The key seems to be grabbing the correct BIOS rom (the US retail one) and putting it named like this "IPL.n64" in the mupen64plus folder of retroarch/system. A quick google search for that exact name shall lead everyone to the correct file. Name your two roms like indicated on the page linked above ( F-Zero X (USA).z64 and F-Zero X (USA).z64.ndd and load the former. Heavy guitar riff upcoming 😉

I know it this thread is quite aged, but I was recently facing the same challenge, trying to get Arculator 2.1 (latest) to boot the games directly. And what can I say, it does work! So in case someone still stumbles over this thread: Here's what needs to be done: 1.) Link the emulator to execute the standard "Arculator.exe" file 2.) For every rom file you want to boot, a config file needs to be created. To do that, run Arculator.exe outside of Launchbox. The Arculator Configuration Manager pops up. Click on "New", bottom left icon. Name the file anyway you want (it should resemble your game to easily detect, of course), but do not have blank spaces in the name. Important... 3.) After selecting the machine type, only thing I did was to set the Memory to max (16 MB), so all games would load up. Hit ok. Your freshly created config file appears within the installation folder of Arculator, under /configs. Open the file you just created, extension is .cfg, in any text editor. 4) in line 2, we can pre-mount the virtual disc. Point to the rom file here, for me this is "Z:\EMULATION\ACORN ARCHIMEDES\Fireball II (1990)(Cambridge International).adf" and save. 5) Repeat steps 2-4 for each game you want to start via LB. 6). Now import your ROM files as you normally would into LB, using the Emulator you linked to Arculator.exe. 7.) Now we have to tell arculator to load the config (cfg) where we pointed the rom path to already. This we do in the Edit Game section -> Emulation -> Use Custom Command-Line Parameters. Here the name of the config file, which sits in the Arculator install directory (remember, folder name is "/configs") needs to be entered, BUT without the file extension. Hit ok. 8.) Voilá, Arculator.exe automatically picks up the config file, reads the path to the rom file and preloads it in drive 0, all ready for you to boot! Only thing I have not figured out yet is how to close out of Arculator without the Confg Manager remaining open...