MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×
Search the Community
Showing results for tags 'games explorer'.
(Thread inspired by Dr. Flay's thread: https://forum.vivaldi.net/topic/38561/windows-7-old-games-failing-to-run) Ever since Games Explorer was introduced in Windows Vista, it has caused problems for users with limited access to the internet. Most affected users would have already disabled it by editing GameUX's registry settings or by unregistering the dll (GameUX.dll), but last month Microsoft has taken the domain the Games Explorer system used to phone for game-related metadata and updates out of commission (specifically: "https://games.metaservices.microsoft.com/games/SGamesWebService.asmx"), thus the problem will also show for users which have permanent connection to the internet. Symptoms related to this problem: Game fails to open, but their processes can be seen in the taskmgr The rundll32.exe process related to gameux.dll spikes up to >50% of CPU usage Running a second copy of the game or renaming the game executable works around it Any old game that has been added by Games Explorer itself is affected to this problem, since Windows is using the rundll32.exe process to check the game updates before launching the game. Note that you can't remove said games from Games Explorer itself, only hide it. Even changing the options within the Games Explorer to never check online for game updates and news won't fix this problem. The fix which tackles the problem at its core is to use these registry files provided by user UCyborg (Make sure to read the whole post!): The second fix (or rather a workaround) which is more simpler, but doesn't remove the problem at its core (less recommended than the first one): All you have to do is to open regedit, go to this key: HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\GameUX\ServiceLocation Changing the server address in the "Games" value to either '127.0.0.1', 'localhost' or '0.0.0.0' ought to fix it.