Hello Valve employees.

Some games like Homefront, Call of Duty®: Black Ops, Aliens vs Predator (2010 version) and others that provides "Updating Executable" process now makes those games become unplayable due to unknown bug, because I verified about waiting for Updating Executable and 15 seconds later, the process stops and makes me have to retry it, so I did it, it failed again.

This problem effects Steam Client for Windows and Linux or maybe Steam Client itself generally.

I can't play those games anymore like I used to, because of the corruption of updating executable process. I added steam_appid.txt to the game with correct match of the Steam AppID number and it still rejected. It will automatically cancel the process without a reason.

Same here, I can't play AVP2010 anymore because the launcher is stuck on "updating executables"
I've posted a negative review to explain this problem because I don't want other people to buy it, since it is on sale now

Steam shouldn't legally be able to sell broken games, especially if the breakage is directly caused by Steam's own DRM, as it appears is the case with AvP(2010).

Originally posted by Valtharsus:

Steam shouldn't legally be able to sell broken games, especially if the breakage is directly caused by Steam's own DRM, as it appears is the case with AvP(2010).

However, they're still there, all they need to do is fix updating executable process.
Yes, patience are required. So I disagree what you said.

Originally posted by Romactu:

However, they're still there, all they need to do is fix updating executable process.
Yes, patience are required. So I disagree what you said.

Until they do fix it, it is broken, they're selling a broken product.

A game that is broken is classified as having a "Major Fault," which is grounds for a full refund. Yet Steam refuses to provide a refund after 14 days(which were spent looking for a workaround). A "Major Fault" as no expiry date for a refund if the fault was present at purchase. As this fault was, and still is.

The support options for AvP(2010) disallow the "Steam Support" option. Even though the problem is on Steams end.

A different user had already lodged a support ticket with SEGA a while ago, but the issue still remains, and if I'm not mistaken, Rebellion has lost the rights to AvP(2010), so no remedy can be forthcoming from them.

Steam either needs to issue full refunds, or fix the Deus damnatus problem they've perpetuated.

Originally posted by Valtharsus:

Originally posted by Romactu:

However, they're still there, all they need to do is fix updating executable process.
Yes, patience are required. So I disagree what you said.

Until they do fix it, it is broken, they're selling a broken product.

A game that is broken is classified as having a "Major Fault," which is grounds for a full refund. Yet Steam refuses to provide a refund after 14 days(which were spent looking for a workaround). A "Major Fault" as no expiry date for a refund if the fault was present at purchase. As this fault was, and still is.

The support options for AvP(2010) disallow the "Steam Support" option. Even though the problem is on Steams end.

A different user had already lodged a support ticket with SEGA a while ago, but the issue still remains, and if I'm not mistaken, Rebellion has lost the rights to AvP(2010), so no remedy can be forthcoming from them.

Steam either needs to issue full refunds, or fix the Deus damnatus problem they've perpetuated.

That's a whole point, selling games even they're broken right now is what certain gamers want, it's just Valve employees needs to fix the issues. (That's all)
Rejecting a refund because of 14 days limit is also a whole point, it's what make game developers/publishers a money. I've been having issues with Homefront and all I got to do is reinstall the game, launch to see the process is working, if the stopped shortly reboot Steam and try again and then wait until the rest of the requirements are set to be ready is all I got to do sometimes. Games like AVP 2010 is strictly to updating executable process to make sure it only works if you're using Steam Client with supported Operating Systems, which it means it's not playable like it used to anymore and a lot of people aren't happy about that and I don't blame them. Also, I already contact with Steam Support team, they're updating Steam to see it will fix the problem.

Originally posted by Romactu:

Also, I already contact with Steam Support team, they're updating Steam to see it will fix the problem.

Fingers crossed that they'll actually follow through.

Just gave it a go. AVP will not launch. It gets stuck on "updating executable" when attempting to launch the game. This seriously needs to be fixed.

Originally posted by Romactu:

Originally posted by hex_eye:

Just gave it a go. AVP will not launch. It gets stuck on "updating executable" when attempting to launch the game. This seriously needs to be fixed.

You should be able to play the game now.
For now on, only if you're on Steam Beta instead of Steam Stable.

Because when I tried to set my Steam launch to Beta from stable due to find out something handy and interesting, apparently not only they done some changes on Beta mode, they also fixed an issues for "Updating Executable" process, so that's why I'm happy with a Beta mode and I already talked to Steam moderators for that thought.

Just a heads up! Not working on my end with Steam Beta, still got updating executable, been deleting the .exe’s and validating, gonna leave a negative review to advise others to avoid this until fixed.

Originally posted by cuttlersan:

Originally posted by Romactu:

You should be able to play the game now.
For now on, only if you're on Steam Beta instead of Steam Stable.

Because when I tried to set my Steam launch to Beta from stable due to find out something handy and interesting, apparently not only they done some changes on Beta mode, they also fixed an issues for "Updating Executable" process, so that's why I'm happy with a Beta mode and I already talked to Steam moderators for that thought.

Just a heads up! Not working on my end with Steam Beta, still got updating executable, been deleting the .exe’s and validating, gonna leave a negative review to advise others to avoid this until fixed.

I've remove that reply since it also did not work for me either anymore.
Thanks for a heads up reminder.

No problem! Appreciate all your follow up on the game; darn shame Steam bricked it and then ignored the problem they made :(

Originally posted by cuttlersan:

No problem! Appreciate all your follow up on the game; darn shame Steam bricked it and then ignored the problem they made :(

Yea, it's a shame for them to do this, at least an older version called AVP Classic 2000 compared to AVP (2010) is still playable.

Bump.

I'm having an issue in the latest beta. Not sure when it started, just noticed today due to Just Cause 2 re-installation/re-verification where "Updating Executable" shows when you try to launch the game, and the game does not launch. Instead, Steam crashes and a "The Steam Client Service service terminated unexpectedly. It has done this 4 time(s)." System event is logged.

It hard closes the steam client and when you restart it you have to log in again etc. etc.

This also happens with "verify game files" which I'm guessing both are triggering an update check using a broken mechanism. This seems only an issue with the "Updating Executable" method (I'm guessing byte-patching?). I also re-downloaded Metro 2033 and did not have this issue, starting and verifying game files with that is fine.

An issue with Just Cause 2 that I've seen (so far).

Reverting to the regular client does seem to fix this particular issue (Updating Executable/Verify Game Files crash).

In the changelog today:
"Fixed regression causing Steam crash when running installscripts for certain games"

This did NOT fix the "Verify Integrity of Game Files" crash, reproducible if you install Just Cause 2 and try to verify it, the steam client will crash without error and the following entry is created in the "System" event log:
"The Steam Client Service service terminated unexpectedly. It has done this 6 time(s)."