Error when running sfcfix.exe : Entry Point Not Found

W

wasinu

Member
Joined
Oct 3, 2015
Posts
19
My windows server 2008 R2 has problem when run MMC, active directory users.. and other administrative tools . They show message : Not enough storage is available to complete this operation.
I have tried to run sfc /scannow but there not success.
I have tried to run DISM /online /Cleanup-Image /ScanHealth but not success too.

When I try to run SFCFIX.EXE. It appear error "The procedure entry point HttpIsHostHstsEnabled could not be located in the dynamic link library WININET.dll.
Can someone help me ? Thank you.
 

Attachments

Hello and welcome!

Make sure you have a good backup of any important data and system state information for this server.

From the symptoms you describe and the error messages in the log file, I suspect that the filesystem needs checking.

I do have some questions:
Have you run chkdsk on this server recently?
Has this server had any disk related warnings or alerts of any kind?
Is the volume Windows is installed on using any kind of RAID?
 
Clear Transactional Logfiles
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good, especially if the computer is not experiencing these exact issues. Do not attempt this fix unless instructed to do so. If you are after assistance, please start a thread of your own.


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it one at a time and press enter after each one.
    Type Y and press enter if you are asked "Are you sure?" to any line. Ignore any failure messages, they are perfectly normal and nothing to worry about.

fsutil resource setautoreset true %SystemDrive%\

attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
del %SystemRoot%\System32\Config\TxR\*

attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
del %SystemRoot%\System32\SMI\Store\Machine\*.blf
del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms​

When these commands are complete, restart the computer.

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.
 
Looks good.

Check for Windows Updates and pick one to install.

If it fails, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
 
I still can not use windows update because of this error
error2.png

and I also still have 3 error problems like these
error.png

First one (WININET.dll) : appear when try to use programs or computer Manage ...
Second one (MMC): appear when try to use MMC related
Last one (inetcpl.cpl): appear when try to use programs or windows function which need to use browser

and from the last CBS log I found this error message here
POQ 132 ends.
2015-10-09 02:08:23, Info CSI 00000309 [SR] Verify complete
2015-10-09 02:08:23, Info CSI 0000030a [SR] Repairing 1 components
2015-10-09 02:08:23, Info CSI 0000030b [SR] Beginning Verify and Repair transaction
2015-10-09 02:08:23, Info CSI 0000030c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-10-09 02:08:23, Info CSI 0000030d [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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
2015-10-09 02:08:23, Info CSI 0000030e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-10-09 02:08:23, Info CSI 0000030f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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
2015-10-09 02:08:23, Info CSI 00000310 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-10-09 02:08:23, Info CSI 00000311 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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
2015-10-09 02:08:23, Info CSI 00000312 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-10-09 02:08:23, Info CSI 00000313 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-10-09 02:08:23, Info CSI 00000314 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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
2015-10-09 02:08:23, Info CSI 00000315 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-10-09 02:08:23, Info CSI 00000316 Repair results created:
Click to expand...

Thank you
 
zcomputerwiz
Looks good.

Check for Windows Updates and pick one to install.

If it fails, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.​
Click to expand...

I try to offline update the MS15-65 IE update (KB3065822) which someone suggest me to install to fix winninet.dll error, but finaly not success. This is the CBS log after try to install this update patch.
 

Attachments

Code: 
12: Hard Link File: Source = [l:264{132}]"\SystemRoot\WinSxS\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.17126_none_e460a5c5b6c8b99e\wininet.dll", Destination = [l:70{35}]"\??\C:\Windows\System32\wininet.dll"
13: Hard Link File: Source = [l:264{132}]"\SystemRoot\WinSxS\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_11.2.9600.17126_none_71b1585866ce382f\inetcpl.cpl", Destination = [l:70{35}]"\??\C:\Windows\System32\inetcpl.cpl"
2015-10-03 19:14:31, Info                  CSI    00000331 Hashes for file member \??\C:\Windows\System32\wininet.dll do not match actual file [l:22{11}]"wininet.dll" :
  Found: {l:32 b:PU61IQAzC7JI/oSlpCUgKQzmfC/m0VseykfQpdstJxE=} Expected: {l:32 b:aaa64BWCxbhND48zuECK/aMqP6Sf86yRXPuJ/Yl91bg=}
2015-10-03 19:14:31, Info                  CSI    00000332 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"wininet.dll" from store
2015-10-03 19:14:31, Info                  CSI    00000333 Hashes for file member \??\C:\Windows\System32\inetcpl.cpl do not match actual file [l:22{11}]"inetcpl.cpl" :
  Found: {l:32 b:RviFszJe6zn6alZJ9aSaXR8gN6mm6FgM1tddabMApoc=} Expected: {l:32 b:kt+4RxybbX9d7zViVgAQhu+T0RR/9ldb14cwrIhgTJg=}
2015-10-03 19:14:31, Info                  CSI    00000334 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"inetcpl.cpl" from store

These files have been replaced because they were corrupt. They may need to be registered.

I see this error as the cause for the update failure:
Code: 
Not enough storage is available to complete this operation.

How much memory (RAM) is installed total and how much is available?

Run Task Manager and sort the running processes by memory use to find out which is using the most.
 
Try running an elevated command prompt (should show the current directory as C:\Windows\System32\), then copy and paste the following command into the window and press enter.

regsvr32 wininet.dll

Let me know the result.
 
Try running Computer Management and see if you get the same error message as before.
 
Log (Attachment) : after running KB947821 (SURT) on my windows 2008 server R2 standard 64 bit. Thank you
 

Attachments

I'd like to take a look at the event logs.

Event Log Collection

  • Download VEW by Vino Rosso here: VEW.EXE
  • Right click the file and select Run as administrator and click Continue or Allow at the User Account Control Prompt.
  • Click the check boxes next to Application and System located under Select log to query on the upper left.
  • Under Select type to list on the right click the boxes next to Error, Warning and Critical (not XP).
  • Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run.
  • Once it finishes it will display a log file in notepad.
  • Copy and paste its entire contents into your next reply.


Are there any repair attempts that you have made previously such as replacing or copying files, editing the registry, etc?
 
You must log in or register to reply here.

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

Back
Top