Cannot get MSFS to run as all I get is “gaming service is not running” …but it is. Any ideas Huston !
Had an update to Windows 11 ( insider programme) today and am wondering if Microsoft broke something.
Jeeez
Re-install gaming services.
In windows seacrh bar type
powershell
right click on powershell and select run as administrator
Copy/paste into powershell window (right click to paste into powershell window)
Remove-Item -Path “HKLM:\SYSTEM\CurrentControlSet\Services\GamingServices” -Recurse
press enter
Copy/paste into powershell window (right click to paste into powershell window)
Remove-Item -Path “HKLM:\SYSTEM\CurrentControlSet\Services\GamingServicesNet” -Recurse
press enter
//////////////////////////////////////////
Restart PC.
/////////////////////////////////////////
Run powershell as administrator.
Copy/paste into powershell window (right click to paste into powershell window)
start ms-windows-store://pdp/?productid=9MWPM2CQNLHN
Click Get
I’m also involved in the insider program. I had that issue all day yesterday and this morning. Reverted back to previous build and all is well again
1 Like
I tried all the troubleshooting including the one you posted to no avail. The new build has or causes file corruption as certain files are missing and cannot be located. I simply reverted back to the previous build and all is well.
2 Likes
I think this is your issue. If you’re using beta software, when stuff that normally works stops working after an update, you can pretty much point to it as being the issue.
The latest build of Wn 11 has broken Gaming Services.
You need to remove Gaming services from the Registry, and reinstall a fresh copy, then update it.
Search for Gaming Services will not start.
I had to do this today.
The replies above do much the same thing.
Martin.
Yes I think it is something to do with the Win 11 insider update I had yesterday. This morning I have had an update for Win 11 and I will now check if this is the fix to this issue that I and some others might have had or are still having. Oh boy…if it’s not Asobo then it’s Microsoft.
Yup… it was the latest insider programme update from Microsoft. Went back to previous build and all is working again. Tut tut.
