Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If so, your problem might be related to the Windows Games Explorer service having become dysfunctional in the past week. Many older games suddenly refuse to start on Windows 7 because they're integrated into the Games Explorer service and waiting for a response from a Microsoft server that appears to have gone down some time around the 8th of June.
I only know this because one of the older games I play, Guild Wars, is also affected by this issue and we've figured out some workarounds while we wait for the developers to patch out the Windows Games Explorer dependency.
Since older singleplayer games like this are unlikely to get updated, here are the workarounds we've been using to bypass the Windows Games Explorer service and force the game to launch:
* Start the game twice. If Steam doesn't allow you to open it again whilst it's already running, open task manager and close the first instance of the game, then start it again and it should start the 2nd time (the first time it tries to invoke rundll32.exe and as long as you leave that process alone it should bypass it the 2nd time).
* For a more permanent solution you can try to rename gameux.dll in C:// Windows / SysWOW64 (after taking ownership and adjusting permissions). This will break the Windows Games Explorer service for all 32-bit games and should allow you to bypass it permanently.
I always try to start the game from the Steam library
Need more info about the second:
rename gameux.dll in.....what? whats the new name
I found gold here! You just answered a big question I've had for days!
Rome used to lauch the first time and work OK in my PC, but suddenly I started having this issue you mention. I had to start the game, then kill the process and restart it; I also noticed run32.dll was invoked, and it would take my CPU to 100% usage, so the game ran terribly.
I renamed C:\Windows\SysWOW64\gameux.dll to a random name, and now Rome is working as before. Thanks a lot man!
https://steamcommunity.com/app/4760/discussions/0/1646544348824561996/