Solved BMS 4.37 Startup error: Could not create device on adapter
-
@Tumbler31 I know! Particularly annoying that the
createDeviceOnAdapter
call works for the 4.35 install I have.
Is the direct x installer available separately anywhere? Just wondering if the silent install is failing somehow and not logging anything.
-
Nevermind. Assuming I’ve got the right one: https://www.microsoft.com/en-gb/download/details.aspx?id=8109
Installing from this didn’t resolve the issue either. -
@Tumbler31 my Windows 11 is already up to date with KB5021255. I am also running on Nvidia Game Ready Driver 527.56. I also tried reinstalling my directX runtime, but to no avail. I still get the same error.
-
Same issue, i’m on W11 22H2 with the newest AMD drivers. Installed DirectX. Windows is up to date, including KB5020044 and KB502155.
-
@rubbereend said in BMS 4.37 Startup error: Could not create device on adapter:
Same issue, i’m on W11 22H2 with the newest AMD drivers. Installed DirectX. Windows is up to date, including KB5020044 and KB502155.
I’m running Win11 Pro 22H2 build 22623.1037 and Nvidia 527.56. I also run (from framerate issues a ways back in VR on IL-2/DCS) a Holoshell shut down batch file that may not even be necessary anymore, and my Nvidia drivers are “naked”, installed by running Display Driver Uninstaller and then running NVCleanstall and only installing the Drivers (and PhysX and Sound if you use them, if not, ONLY the drivers. No Telemetry, No GeForce Experience bloatware. Other than that I have done nothing special to get this working, good luck!
-
I can confirm that when I unplug my Reverb G2 and reboot the game runs fine. I can then plug in my Quest 2 via Link cable and the game runs in VR just fine. When I unplug the Quest 2 and plugin the Reverb G2 the game no longer works. So, I am definitely leaning towards a windows update issue that has broken this game with WMR. I am currently running Windows 11 22H2 and cannot roll back. I am in the insider programs beta branch so I guess it’s a waiting game or maybe there is something in Falcon BMS 4.37 that can be adjusted for it to work. I guess I’ll have to wait for smarter people to come up with something or Microsoft to fix Windows 11 again.
-
I was never impressed by HP hardware…
Don’t know what they did with their headset to be so different from the others…
-
I found a fix for windows 11:
I’ve updated to the latest beta version of windows 11 with a bat file that you can find here: https://github.com/abbodi1406/offlineinsiderenroll/releases
then, I’ve stopped the holographic shell with a bat file that you can find here:
https://forums.flightsimulator.com/t/win-11-update-causing-stutters/543631/127(if you are completely new to bat files, copy the code: "
@echo off
logman stop HolographicShell -ets
" without the 2 “” and paste it in a .txt file. Then rename it to yourfilename.bat) -
@vps_zen I can confirm this works without installing beta. I’ve ran the bat file and then game launches correctly.
-
for clearer copy/pasta:
@echo off logman stop HolographicShell -ets
this is great news, if this works for everyone
-
@johnnyj71 again, if you are on the Windows Insider Beta release section you should be running 22H2 22623.1037, that is not the issue as i’m in the WI program also. Try the Holoshell fix shown above, if it works you can set it as a Task to run at every start up…
-
-
You don’t need to be on the windows insider track for this to work. You just need the bat file described by @vps_zen and @airtex2019
Thank you, both of you!
-
-
-
@airtex2019 - Can confirm that it works for me even on my AMD setup, so it seems HoloShell is the cause
Now I wish I wasnt so damn hungover for VR haha
-
Yep, running that command did work just fine for me. Thanks for the heads up everyone.
-
@LockeyNoS7even said in BMS 4.37 Startup error: Could not create device on adapter:
You don’t need to be on the windows insider track for this to work. You just need the bat file described by @vps_zen and @airtex2019
Thank you, both of you!
All credit to @Icer who told us what was working for him and what to google for … and @vps_zen for confirmation! I’m just a bystander, don’t have Win11 or VR, so can’t even help test or debug.
I will however send some pointed questions to people I know on the Hololens / WMR team…
-
@vps_zen said in BMS 4.37 Startup error: Could not create device on adapter:
I found a fix for windows 11:
I’ve updated to the latest beta version of windows 11 with a bat file that you can find here: https://github.com/abbodi1406/offlineinsiderenroll/releases
then, I’ve stopped the holographic shell with a bat file that you can find here:
https://forums.flightsimulator.com/t/win-11-update-causing-stutters/543631/127(if you are completely new to bat files, copy the code: "
@echo off
logman stop HolographicShell -ets
" without the 2 “” and paste it in a .txt file. Then rename it to yourfilename.bat)By doing this….will VR still work?
-
@cougar56th said in BMS 4.37 Startup error: Could not create device on adapter:
@vps_zen said in BMS 4.37 Startup error: Could not create device on adapter:
I found a fix for windows 11:
I’ve updated to the latest beta version of windows 11 with a bat file that you can find here: https://github.com/abbodi1406/offlineinsiderenroll/releases
then, I’ve stopped the holographic shell with a bat file that you can find here:
https://forums.flightsimulator.com/t/win-11-update-causing-stutters/543631/127(if you are completely new to bat files, copy the code: "
@echo off
logman stop HolographicShell -ets
" without the 2 “” and paste it in a .txt file. Then rename it to yourfilename.bat)By doing this….will VR still work?
ETS is “event trace system” or something along those lines … it’s just performance-data logging, in Windows platform.
logman is the command line tool to manage and enable/disable ETS tracing sessions.
I have no idea why this logging is “on” by default … or why it would impact functionality (vs just make perf maybe tiny bit slower) … apparently it does something that makes it look like a graphics-pipeline debugger is hooked up?
And no idea why MS thinks KB5020044 has fixed this problem, when it clearly hasn’t.
-
@cougar56th said in BMS 4.37 Startup error: Could not create device on adapter:
@vps_zen said in BMS 4.37 Startup error: Could not create device on adapter:
I found a fix for windows 11:
I’ve updated to the latest beta version of windows 11 with a bat file that you can find here: https://github.com/abbodi1406/offlineinsiderenroll/releases
then, I’ve stopped the holographic shell with a bat file that you can find here:
https://forums.flightsimulator.com/t/win-11-update-causing-stutters/543631/127(if you are completely new to bat files, copy the code: "
@echo off
logman stop HolographicShell -ets
" without the 2 “” and paste it in a .txt file. Then rename it to yourfilename.bat)By doing this….will VR still work?
Yes, and with better framerates/frametimes!
-
This worked for me as well! Thanks everyone!
-