• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

[SOLVED] Trying to install .NET Framework

I tried all that. Windows had a look at my computer and said it a problem with my registry and they can fix it but it's not part of their free service and I would have to pay for it
 
Hello Gibbo, and welcome to Sysnative :)

Linked here is an article which details how to enable or disable verbose Windows Installer logging. http://support.microsoft.com/kb/223300

I want you to:
1) Enable verbose Windows Installer logging (use the Fix-It at the above link)
2) Re-run Windows Update. Try to install any updates you are offered.
3) Download the KB update in question and try to install it manually: Download Microsoft .NET Framework 4 (Web Installer) from Official Microsoft Download Center
4) Disable verbose Windows Installer logging using the matched pair Fix-It from the link I provided.
5) Run collect.exe and copy to Desktop, zip up & upload both %temp%\vslogs.cab & C:\Windows\Logs\CBS folder. See here for details: Instructions to collect .NET Framework 4 and Visual Studio 2010 setup logs - VarunGupta - Site Home - MSDN Blogs

.net issues are sometimes quite difficult to fix. If it's Windows Installer store corruption we don't have a chance. If it's most other things a forced uninstall will do the trick - but we first need to check whether there's anything which could make the situation more complicated or unstable. In such a situation we have to attempt a fix, and it's a bit hit and miss as to whether your error will be fixable or not. Still, we'll hope for the best. With any luck the logfiles will reveal some useful information we can make use of.

Fingers crossed :)

Richard
 
Last edited:
Hello Gibbo, and welcome to Sysnative :)

Linked here is an article which details how to enable or disable verbose Windows Installer logging. http://support.microsoft.com/kb/223300

I want you to:
1) Enable verbose Windows Installer logging (use the Fix-It at the above link)
2) Re-run Windows Update. Try to install any updates you are offered.
3) Download the KB update in question and try to install it manually: Download Microsoft .NET Framework 4 (Web Installer) from Official Microsoft Download Center
4) Disable verbose Windows Installer logging using the matched pair Fix-It from the link I provided.
5) Run collect.exe and copy to Desktop, zip up & upload both %temp%\vslogs.cab & C:\Windows\Logs\CBS folder. See here for details: Instructions to collect .NET Framework 4 and Visual Studio 2010 setup logs - VarunGupta - Site Home - MSDN Blogs

.net issues are sometimes quite difficult to fix. If it's Windows Installer store corruption we don't have a chance. If it's most other things a forced uninstall will do the trick - but we first need to check whether there's anything which could make the situation more complicated or unstable. In such a situation we have to attempt a fix, and it's a bit hit and miss as to whether your error will be fixable or not. Still, we'll hope for the best. With any luck the logfiles will reveal some useful information we can make use of.


Fingers crossed :)

Richard

Tried the first 1-4 steps didn't wouldn't work
 

Attachments

Hello Gibbo, and welcome to Sysnative :)

Linked here is an article which details how to enable or disable verbose Windows Installer logging. http://support.microsoft.com/kb/223300

I want you to:
1) Enable verbose Windows Installer logging (use the Fix-It at the above link)
2) Re-run Windows Update. Try to install any updates you are offered.
3) Download the KB update in question and try to install it manually: Download Microsoft .NET Framework 4 (Web Installer) from Official Microsoft Download Center
4) Disable verbose Windows Installer logging using the matched pair Fix-It from the link I provided.
5) Run collect.exe and copy to Desktop, zip up & upload both %temp%\vslogs.cab & C:\Windows\Logs\CBS folder. See here for details: Instructions to collect .NET Framework 4 and Visual Studio 2010 setup logs - VarunGupta - Site Home - MSDN Blogs

.net issues are sometimes quite difficult to fix. If it's Windows Installer store corruption we don't have a chance. If it's most other things a forced uninstall will do the trick - but we first need to check whether there's anything which could make the situation more complicated or unstable. In such a situation we have to attempt a fix, and it's a bit hit and miss as to whether your error will be fixable or not. Still, we'll hope for the best. With any luck the logfiles will reveal some useful information we can make use of.


Fingers crossed :)

Richard

Tried the first 1-4 steps didn't wouldn't work

Hello :)

Could you please elaborate a little on "wouldn't work"? What precisely went wrong?

In general those instructions aren't going to fix the problem. First they turn on extended (verbose) logging, such that more information is saved about *what* is going wrong and *why* to ease diagnosis, then we re-run .net (which will fail again, but this time saving more detailed diagnostics info), then we disable the extra diagnostic info collection, and finally you use collect.exe to gather together all of the diagnostic information into one place so you can upload it here and I can analyse it.

Richard
 
Awesome :)

Hold down the Windows Key, press R and then release both. The Run dialogue should open. Type in %temp% and press enter. A folder should open. Inside there should be vslogs.cab.

I really didn't do a great job of explaining that first time around. I'm very sorry about that.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top