Unable to Update/Repair/Remove .Net Framework 4.5 Error Code 66A

There are a lot of errors there!

Please run the following command in an Elevated Command Prompt....

regsvr32 %windir%\system32\rsaenh.dll
ICACLS C:\ProgramData\Microsoft\Crypto\RSA
netsh p2p pnrp cloud show names
netsh p2p pnrp peer resolve 0.testingpnrp


post the results

Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

You could try a repair install

Repair Install

Open an Elevated Command Prompt, and run the following command

NETSH WINSOCK RESET

reboot on request, then run the following commands again

ICACLS C:\ProgramData\Microsoft\Crypto\RSA
netsh p2p pnrp cloud show names

Please run the following command

REG QUERY HKLM\SYSTEM\CurrentControlSet\services\WinSock2 /S >>%userprofile%\desktop\winsock2.txt

It will place the file winsock2.txt on your desktop - please attach that to your reply.

I wish I knew which 'underlying system' it was talking about!

I'm asking for assistance - don't run away :)

NoelDP said:

I wish I knew which 'underlying system' it was talking about!

I'm asking for assistance - don't run away :)

This may be your "underlying system"

This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:

that the WINSOCK.DLL file is in the current path,
that the WINSOCK.DLL file is from the same vendor as the underlying protocol stack. They cannot be mixed and matched (WinSock DLLs must be supplied by the same vendor that provided the underlying protocol stack).
that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.
the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.

Source 2nd post: https://secure.dslreports.com/forum/r25790234-