Question : Installing .NET Framework 3.5 errors

I am getting errors when installing microsofts .net framework 3.5.. This is the installation log.

I'm not sure what I should do to solve it, as I went to install it because I'm getting a similar issue with installing a game, and someone stated to install the framework, but now after a uninstall/reinstall, this occurs here. I'm not sure what I should do! I am using Windows Vista Home Premium 64bit.  

I have attached the log file here, if you have any ideas, it would be great.. Thanks!

[02/13/10,08:46:33] Microsoft .NET Framework 3.5: [2] ERROR:An error occurred during the installation of assembly 'policy.9.0.Microsoft.VC90.CRT,version="9.0.21022.8",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32-policy"'. Please refer to Help and Support for more information.
[02/13/10,08:46:33] Microsoft .NET Framework 3.5: [2] ERROR processed; exception was thrown for retail build
      Developer Comment:  
      Build Time:  Thu Dec 11 14:04:18 2003
      DWORD:  1603
[02/13/10,08:46:33] setup.exe: [2] ISetupModule::SetManager() failed in ISetupManager::LoadSetupObjectGuid() : vs_setup.dll
[02/13/10,08:46:33] setup.exe: [2] CSetupManager::LoadSetupObjectname() - Failed in call to LoadSetupObjectGuid() for strName:  in file: vs_setup.dll
[02/13/10,08:46:33] setup.exe: [0] LoadComponent(), LoadSetupObjectName failure: vs_setup.dll
[02/13/10,08:46:33] setup.exe: [0] LoadComponent failed in ISetupManager::LoadComponentsFromDBObject(): vs_setup.dll
[02/13/10,08:46:33] setup.exe: [2] CSetupManager::LoadDatabaseValues() - Failed in call to LoadComponentsFroMDBObjects()
[02/13/10,08:46:33] setup.exe: [2] CSetupManager::RunIntro() - Failed to Load Database Values
[02/13/10,08:46:33] setup.exe: [2] CSetupManager::RunLoadSetup() - Failed to Run the Intro
[02/13/10,09:02:45] setup.exe: [2] Unable to launch deletetemp in CSetupManager::RemoveSetupFiles() for szPath: \Microsoft .NET Framework 3.5 SP1\deletetemp.exe
[02/13/10,09:13:35] Microsoft .NET Framework 3.5: [2] ERROR:An error occurred during the installation of assembly 'policy.9.0.Microsoft.VC90.CRT,version="9.0.21022.8",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32-policy"'. Please refer to Help and Support for more information.
[02/13/10,09:13:36] Microsoft .NET Framework 3.5: [2] ERROR processed; exception was thrown for retail build
      Developer Comment:  
      Build Time:  Thu Dec 11 14:04:18 2003
      DWORD:  1603
[02/13/10,09:13:36] setup.exe: [2] ISetupModule::SetManager() failed in ISetupManager::LoadSetupObjectGuid() : vs_setup.dll
[02/13/10,09:13:36] setup.exe: [2] CSetupManager::LoadSetupObjectname() - Failed in call to LoadSetupObjectGuid() for strName:  in file: vs_setup.dll
[02/13/10,09:13:36] setup.exe: [0] LoadComponent(), LoadSetupObjectName failure: vs_setup.dll
[02/13/10,09:13:36] setup.exe: [0] LoadComponent failed in ISetupManager::LoadComponentsFromDBObject(): vs_setup.dll
[02/13/10,09:13:36] setup.exe: [2] CSetupManager::LoadDatabaseValues() - Failed in call to LoadComponentsFroMDBObjects()
[02/13/10,09:13:36] setup.exe: [2] CSetupManager::RunIntro() - Failed to Load Database Values
[02/13/10,09:13:36] setup.exe: [2] CSetupManager::RunLoadSetup() - Failed to Run the Intro
[02/13/10,09:18:45] Microsoft .NET Framework 3.5 (x64) 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) 'package'. MSI returned error code 1601
[02/13/10,09:18:48] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) 'package' is not installed.
[02/13/10,09:19:50] Microsoft .NET Framework 3.5 (x64) 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) 'package'. MSI returned error code 1601
[02/13/10,09:19:51] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) 'package' is not installed.

Any suggestions? I do get a similar issue with framework 2.0x as well... So I'm kind of clueless.

Answer : Installing .NET Framework 3.5 errors

- Unnistal them all
- Run some cleaner, like CCleaner for incorrect dlls detection on windows registry
- Reboot
- Install them all using one language only (all installers in english, in example)
- Reboot after each installer if necessary