Skip to content

Published: September 14, 2014 | Applies to:

If you're facing "RunDLL - The Specified Module Could Not Be Found" error every time you start your Windows 8.1 upgraded from Windows 8, fix is here.

Obviously, clean install to Windows operating system is rather better than upgrading your system from older editions. In clean install, although the installation takes few moments to complete but you have to spend some extra time to install your desired software/applications. The main benefit of  clean install is that there is no corrupted or malfunctioned entries remain inside the system. Recently at Microsoft Community, I have seen many users upgrading to Windows 8.1 from Windows 8 have came around following error whenever they start their upgraded system:

RunDLL

There was a problem starting

C:\PROGRA~1\COMMON~1\System\SYSPLA~2.DLL

The specified module could not be found.

As you can see in the above shown image, there is no error code whose reference you can take to fix this issue, even there is no help or support link for this scenario. Users may see up to three identical error dialogs like the one shown above when they start their upgraded Windows 8.1. Initially, you can try SFC /SCANNOW command at administrative Command Prompt and also the DISM commands to fix this problem. Even if the issue persists, try following fix. Please make sure you have created System Restore point before proceeding:

FIX : “RunDLL – The Specified Module Could Not Be Found” In Windows 8.1

1. Download the Autoruns tool form Sysinternals using following link. This is a Microsoft IT Professionals recommended tool to analyse system activities and various processes, you can read more about it on Technet. Once downloaded, unzip it using any decompression software.

DOWNLOAD LINK

2. When you unzip the above downloaded file, under Autoruns folder you will see two applications namely; autoruns and autorunsc. Run the autoruns application by double clicking over it.

3. Now in the below shown window, firstly switch to Everything tab. Next look for the yellow entries which are corresponding to file not found. All you need to do is carefully found out those yellowish file not found entries and press Ctrl + D to delete them individually, or you can right click over an entry and select Delete.

When you finished deleting those entries, you can close Autoruns and restart the machine, problem should be fixed now.

Hope this helps!


SHARE: Facebook Google+ Twitter

14 Comments

  • hi
    i must say it worked!!!
    thank you for your help. i was searching for this more than a week.just today i found it. thanks again!!

  • Hi,

    Thank you so much. It worked perfectly.

  • Thank you for the solution. I had gone through the many solutions for this problem but, only this got me rid of this problem………..Bingo Now. Many thanks again.

  • Hi

    Your solution was a success. Thank You

  • Hey,

    The solution worked,

    Thanks :)

  • Kapil Arya

    ^^ Glad we could help! :)

  • Thanx it worked perfectly

  • Kapil Arya

    ^^ Glad it worked! :)

  • You are a Genius !!! Thank a lot ! I can go to bed now ! ^^

  • Kapil Arya

    ^^ Thanks for feedback :)

  • Hi,
    I tried this solution on Windows XP SP3 and worked :)

    Thanks !

  • Kapil Arya

    ^^ That’s awesome :D

  • Tried deleting the yellow entry within Autoruns and received an access is denied prompt. Not sure what to do next. I am leaning towards resetting my PC.

  • Kapil Arya

    ^^ Are you using built-in administrator account? If not, try using it and see if it works.

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      2 hours ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      2 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      4 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      9 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      10 hours ago

    • Keith Fessey : Ok, so whats the difference between the "recovery key" and t...

      14 hours ago


    Windows Group Policy Troubleshooting