Hi! I recently uninstalled Skyrim from steam and now i want to install it again. However when i try to install it says: The steam server are currently too busy to handle your request. Please try again in a few minutes. It's been like this for a week now. I've tried contacting Steam and steam forums but nothing works.


I've tried everything the Steam support guys are throwing at me and nothing seems to work.

Hello,Thank you for contacting Steam Support.If you are currently running Vista or Windows 7, please complete the instructions in the following link:Title: Windows 7 and Vista TroubleshootingLink:If you are running in Windows XP, take the following steps:1) Exit Steam.2) Go to the "Start" menu, select "Run", type "regedit" and click "OK".3) Navigate to the following registry key: HKEY_CURRENT_USER\SOFTWARE\VALVE4) Right click and select "Permissions"5) Check the "Allow" boxes for "Admin" and "System" for both "Full control" and "Read".The remaining steps apply to *all* versions of Windows.Please also verify the GCF for this game as outlined here:Title: Verifying Game Cache Files (GCF)Link:Note: Files may fail to verify. This is normal and can be ignored.Then test the issue.If you still have difficulty, you may also need to manually run secondary installers required by this game.Exit Steam entirely.Browse to your Skyrim installation folder (Usually C:\Program files\Steam\Steamapps\common\skyrim\)Run the following installers:...\Steamapps\common\skyrim\DirectX10\dxsetup.exe...\Steamapps\common\skyrim\DotNetFX\dotnetfx35setup.exe...\Steamapps\common\skyrim\VCRedist\vcredist_x86.exeReboot your computer and test the issue again.If the issues persist, please complete these guides:Title: This game is currently unavailableLink: Title: Games do not run after 'Preparing to Launch'Link: Further support for this title is handled by a third party support department - please follow the instructions below to contact the support provider to troubleshoot this issue:Title: Skyrim, The Elder Scrolls VLink: 

I've tried all of that.

Try refreshing ClientRegistry.blob
That's the usual solution to these things.