Solved Can't install .NET Framework 3.5.1 KB265411

[Swaggy P]

I always get Error: 80073712 when I try to install it.

 

[NoelDP]

.NET 3.5 is part of the OS - and cannot be installed from external media.


The error message you are getting indicates that the update is also installed.

 

[Swaggy P]

Thanks for the reply. Did you mean "already installed" instead of "also installed"? Thanks again.

 

[NoelDP]

In this context it probably amounts to the same thing.
Just to be on the safe side, please post the results of the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html - then we can be reasonably certain that my analysis is correct (or not!)

 

[Swaggy P]

Well, I've followed all of the Windows Update Posting Instructions Steps, and here are the results

1. I downloaded and installed the System Update Readiness Tool, and then I tried to install the update again.....BINGO!!! It worked!!! Thanks.
2. I did an SFC Scan. The results are saying that it found errors, but Windows cannot fix it. Should I just ignore the result, or create another thread about this? After that, I created a .zip folder of the CBS Folder. (C: Windows/Logs).

 

[NoelDP]

Please post the logs - if there are more errors that need fixing , we may as well do it now, or you'll end up with more problems later.

 

[Swaggy P]

Here is the CBS log:

 

[NoelDP]

You have one error in the SFC scan -

 Line 5193: 2013-03-25 13:33:12, Info                  CSI    000002f9 [SR] Repairing 1 components
 Line 5194: 2013-03-25 13:33:12, Info                  CSI    000002fa [SR] Beginning Verify and Repair transaction
 Line 5197: 2013-03-25 13:33:12, Info                  CSI    000002fc [SR] Cannot repair member file [l:32{16}]"AuthFWSnapin.dll" of Networking-MPSSVC-Admin, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 5200: 2013-03-25 13:33:12, Info                  CSI    000002fe [SR] Cannot repair member file [l:32{16}]"AuthFWSnapin.dll" of Networking-MPSSVC-Admin, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 5201: 2013-03-25 13:33:12, Info                  CSI    000002ff [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
 Line 5206: 2013-03-25 13:33:12, Info                  CSI    00000302 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:32{16}]"AuthFWSnapin.dll"; source file in store is also corrupted
 Line 5211: 2013-03-25 13:33:12, Info                  CSI    00000304 [SR] Repair complete

There are however a large number of rather strange errors in the rest of the CBS log.

 Line 988: 2013-03-25 13:04:27, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
 Line 992: 2013-03-25 13:04:27, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]

- to pick two examples

I *think* these errors relate to the following files...

Package_for_KB2757638~31bf3856ad364e35~amd64~~6.1.1.2
Package_for_KB2604115~31bf3856ad364e35~amd64~~6.1.1.3

Please run the following commands, and post the results.

ICACLS C:\Windows\Servicing\Packages\Package_for_KB2757638~31bf3856ad364e35~amd64~~6.1.1.2.*
ICACLS C:\Windows\Servicing\Packages\Package_for_KB2604115~31bf3856ad364e35~amd64~~6.1.1.3.*

 

[Swaggy P]

Here they are:


I don't think I copied and pasted right.

 

[NoelDP]

Both results look normal to me - I was expecting to see the wrong permissions for the TrustedInstaller service.
What I don't understand is how we get those errors in the CBS log, but no errors in CheckSUR.

 

[Swaggy P]

What is the error about? (Not that Good with Computer Science)
What are these errors going to do to my computer (in the long run)?
Is it that BIG of a problem?

Thanks again for your help. I really appreciate it.

EDIT:
I forgot to tell you that I've also been getting BSOD errors lately. I downloaded Blue Screen View and the main errors were ntoskrnl.exe and fltmgr.sys.

If you don't mind you can go to this link: http://www.sevenforums.com/bsod-help-support/283850-ntoskrnl-exe-bsod.html#post2339133 and see if you can help me.

Thank you.

 

[NoelDP]

Please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and post the results here - I'll get a specialist to look them over while I snore

 

[Swaggy P]

Here are the dmps:

 

[NoelDP]

Hmm - ther e are rather more errors with MSE than I would like to see

Microsoft Antimalware Real-time Protection has restarted a feature. It is recommended that you run a full system scan to detect any items that may have been missed while this agent was down.
  Feature: Network Inspection System
  Reason: Real-time protection has recovered from an unknown failure. It is recommended that you run a quick scan.

This is rather a worry.

Please download and install Malwarebytes Anti-malware (free version) from http://www.malwarebytes.org/products/malwarebytes_free/ - UNtick 'Enable free trial of MBAM PRO' at the end of the installation - and update it, then run a full scan in your main account, and Quick scans in any other user accounts.

Delete everything it finds
Doing the full MBAM scan with MSE running in the background also forces MSE to inspect all files - so you shouldn't need to run a full MSE scan as well

 

[Swaggy P]

It detected ZERO.

 

[NoelDP]

What other Anti-Virus products have EVER been installed on this machine? - including the one it shipped with?

To answer your earlier question, all updates for Windows use 'Component Based Servicing' - basically each update is made up of small packets of data, and constructed on-the-fly at install time. The resulting files are governed by a set of files which includes Manifest, and Package files, which crosscheck the update before install, and which have self-checked registry entries corresponding.
If anything get out-of-whack the system attempts to repair itself from backups created at install time.
If that repair fails, then the system defaults back to using an older version of the files until the new ones are fixed.
CheckSUR checks the registry entries against its internal database, and the control files against its own set. SFC does a relatively simple check of the file against it's known Hash result, and attempts replacement using the backup if available, and errors out if not.
so a control file should appear in both results if it's corrupted.
However, CheckSUR doesn't have a full listing of all possible variants (It'd be huge if it did) so it's possible for a control file to appear in the SFC listing, but not in CheckSUR. The reverse is also true - but I'm not sure why
I'm pretty sure however that it does cover the two example files I picked out (one day I'll have a couple of hours spare to extract the files from CheckSUR and find out!), so the manifest, or the package, should have appeared in the CheckSUR result.

Hope that helps! - and doesn't confuse you even more.

 

[Swaggy P]

I bought this laptop in 2011. I'm not sure if it was shipped with an anti-virus software. I separately bought Kaspersky, which didn't really work with my laptop. It freezes and hangs whenever I install it. (No Blue Screens though), so I decided not to use it anymore. One of my first ever BSODs (January 2013 - That's why I joined this website) was when I installed some XNA and .NET Framework 4.0 . In order to play a game. - I don't really know if that's the reason why.

Thanks for the info!

-*sighs* I just got a Blue Screen again. -_- Same info ntoskrnl.exe -- According to Blue Screen View. I posted this problem to a different thread and got answers that it is a driver problem.

 

[NoelDP]

Your machine almost certainly came with either McAfee or Norton pre-installed.
We need to run the removal tools for both to be on the safe side.


Download the McAfee removal tool from:

http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Click Save, and save the file to a folder on your computer.
Navigate to the folder where you saved the file.
right-click on MCPR.exe and select 'Run as Administrator' to run the removal tool.

when complete, reboot.

Download the Norton Removal Tool from here https://www-secure.symantec.com/norton-support/jsp/help-solutions.jsp?lg=english&ct=united+states&docid=20080710133834EN&product=home&version=1&pvid=f-home

Close all other programs, then run the tool. When it's complete, reboot the machine whether it asks for it or not.

After the reboot, open an Elevated Command Prompt, and run the following command

NETSH WINSOCK RESET

You'll be advised to reboot - do so.


Once you've done that ,, it may be a good idea to uninstall and reinstall MSE to ensure that it's fully-functional.

 

[Swaggy P]

LOL How Can I FORGET ABOUT NORTON. That's the anti-virus that came with this laptop.

Dmps March 27:

 

[Swaggy P]

Okay, I have done every step that you gave. No BSODs so far. I will report back if it happens.