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:
There was a problem starting
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 10/8.1/8
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.
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!