Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»configmgr»1602»SCCM Configmgr client issue SCClient.exe Entry Point Not Found WININET.dll could not be located in the dynamic link library

    SCCM Configmgr client issue SCClient.exe Entry Point Not Found WININET.dll could not be located in the dynamic link library

    Eswar KonetiBy Eswar KonetiOctober 21, 5:53 pm3 Mins Read 1602 7,419 Views
    Share
    Facebook Twitter LinkedIn Reddit

     

    Few days back ,I was helping friend of mine ,who had some issues with SCCM Client and he was unable to launch Software Center .When he try to open Software Center application,it immediately pop-up with error code as shown below .

    SCNotification has stopped working .

    The procedure entry point HttpsisHostHstsEnabled could not be located in the dynamic link library WININET.dll

    image

    clip_image002

    I tried launching event viewer ,MMC etc but unable to open any of them and all giving same error code as No storage available to perform this operation.

    I tried uninstalling SCCM Client, remove SMS certificates ,delete smscfg.ini ,restart the client and install the client but still get same error.

    How do I fix this issue if reinstalling the client did not help ?

    clip_image001

    If you look at the error message ,it says ,The procedure entry point HttpsisHostHstsEnabled could not be located in the dynamic link library WININET.dll.

    This lead me to replace the existing WININET.dll file from working client in both System 32 and Syswow64 folder .

    Note: In order to perform the following steps,you need to have local administrative rights on the client .

    By default ,this file is owned by trusted installer and if you simply delete /rename this file and copy wininet.dll from working client ,it doesn’t allow you replace the file.

    How to delete\replace the file then ? Well ,we will try to take the ownership of this file and then perform the operation on it.

    Go to C:\windows\system32 folder on problem client ,right click on wininet.dll, Properties ,go to security ,click on Advanced

     

    image

    click on Owner Tab and select Edit

    image

    On the owner tab ,select administrators or user listed in the Change Owner from Trustedinstaller.

    image

    Windows security pop-up appear and proceed to perform these changes.

    clip_image006

    Now ,we have taken the ownership of WININET.dll file .

    We will try to rename the file to something else like WININET_old.dll and then we will copy the file from working client to here.

    Login or access admin$ share on any other working client ,copy WININET.dll file from C:\windows\system32 folder ,paste it on non-working client folder C:\windows\system32

    We need to perform the same procedure as we did above for Syswow64 folder (incase if x64 OS) as well .

    Go to C:\windows\syswow64 and take the ownership of file WININET.dll from trustedinstaller to administrators or other user who has local administrative rights.

    Rename the file to WININET_old.dll .

    Login or access admin$ share on any other working client ,copy WININET.dll file from C:\windows\syswow64 folder ,paste it on non-working client folder C:\windows\syswow64

    Now reboot the client and launch System Center application ,it works as usual without any errors.

    I have no idea what causes this issue and have not spent much time to find the root cause.

    If you have any other better solution which worked, please post it via comments ,I will update the blog post for others.

    Hope it helps!

    Client issue configmgr SCClient.exe Entry Point Not Found SCCM scnotification has stopped WININET.dll WININET.dll could not be located in the dynamic link library
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    SCCM SQL Report – Compare Installed Apps on TWO Different Computers

    July 13, 10:35 am

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.