27% steam update error

[Asrai]

Help me please. I tried this link:

http://steampowered.custhelp.com/cg...XRfbHZsMT0mcF9jYXRfbHZsMj0mcF9wYWdlPTI*&p_li=

But it really does not make sense to me.

 

[All_Steamed_Out]

Hi:


I spent weeks trying to solve this problem. I assume you also get this error message:

'Steam.exe (Main Exception): ERROR: delete of steam.exe failed,Win32
Error 5 'Access is denied'

Steam’s tech support is useless, basically because they choose to blame an infection on your machine instead of their poorly written program. And that is borne out by their lack a suggestion for a real solution on that linked page you list.

After relentlessly digging through the forums, I found this post by someone with a great more experience and skill than I. It worked for me, give it a try. I have pasted his procedure below. Good Luck!

What I Did...
Maybe this isn't an "approved" method, but it allowed me to get into the game after about 2 hours of troubleshooting:

1. Remove any old versions of Steam.
2. Download the Steam client.
3. Download PrcView - a freeware utility that displays running processes. http://www.xmlsp.com/pview/prcview.htm
4. Run PrcView.exe. You'll see a list of running processes. Keep this somewhere visible, so you can monitor it and click on it.
5. Run the Steam.exe
6. You'll see Steam.exe listed in Process Viewer as a running process.
7. Watch it closely.
8. Soon, you'll see SteamTmp.exe launch. When you see this launch, immediately Kill the Steam.exe manually.
9. The SteamTmp.exe will close, and then continue running again as Steam.exe (a new Steam.exe not the one you killed in Step 8 above).
10. Continue updating as normal, and close Process Viewer.
11. Everything should be good to go!

While the above is necessarily perfect, it will circumvent any other SP2, Winblind, A/V, or other apps that could be causing problems with closing of processes in a timely manner.

When I monitored the processes using PrcView.exe, I did notice that eventually, the original Steam.exe would close. Unfortunately, SteamTmp.exe would "time-out" waiting for this to happen.

IMHO, if they simply increased the "time-out" as it waits for the old Steam.exe to close, a majority of users issues would be resolved.... Or, they could simply issue a forced "Kill" of the process themselves...

Not clean, but it works!