Home / there was a problem starting rundll There was a problem starting rundll 30/03/2021 The RunDLL error ‘Tright here was a difficulty starting ~. The specified module could not be found‘ largely occurs once Windows users attempt to open an HDD or external HDD drive. But for some customers, the error only appears when they attempt to open up up a shortreduced that is pointing to an executable stored on this disk.You watching: There was a problem starting rundllThis certain issue is not exclusive to a specific Windows variation and is evidenced to happen on Windows 7, Windows 8.1 and Windows 10.As it transforms out, in a lot of instances, this specific error will happen because of an autorun.inf file stored in the root of the HDD that is either system-defended, read-only and also concealed – this concern is many most likely promoted by some sort of virus infection. If this is the instance, you deserve to deal with the difficulty quickly by deleting eincredibly autorun.inf file that can be leading to the difficulty – You deserve to either execute this using a CMD prompt (Method 1) or by utilizing Regisattempt Editor (Method 2).However before, the concern deserve to likewise be resulted in by logical errors on the influenced drive (Method 3), a partly rerelocated infection (Method 4) or a significant situation of device file corruption (Method 5).Method 1: Deleting the autorun.inf fileAccording to various user reports, this worry is popularly brought about by what’s recognized as a ‘shortreduced virus’. This type of malware hides all your records and also folders, then replaces them all with shortcuts that look specifically the same. Nowadays, eexceptionally major AV suite is equipped to detect and remove this type of protection danger, yet the trouble is, not all of them are capable of removing the autorun.inf file that was formerly created.If this happens, the drives affected by the virus can come to be inavailable as a result and show the ‘Tright here was a trouble starting ~. The specified module could not be found‘ once the user tries to access them.If this scenario is applicable, you deserve to fix the problem by using the terminal to navigate to the root area of your tough disk and also deleting the autorun.inf file – Many likely, it has read-just properties, it’s covert or it’s a device safeguarded.The instructions below will certainly assist you to get rid of it and also fix the issue:Press Windows essential + R to open up a Run dialog box. Next off, inside the text box, type ‘cmd’ and also press Ctrl + Shift + Enter to open up up a CMD window via elevated privileges. When you’re asked to provide governmental access using the UAC (User Account Control), click Yes to provide admin access.Running Command also PromptOnce you’re inside the elevated CMD prompt, type the following command in order to navigate to the root place of the impacted drive:CD X:Note: Keep in mind that X is simply a placeholder for the affected drive. Replace it according to the letter matching to the drive-in your certain scenario.Once you regulate to get to the root area of the impacted drive, type or paste the following areas in order and also push Enter after each one to delete the autorun.inf file forcefully:Attrib -r -s -h d:autorun.infDel /F d:autorun.infAfter the procedure is finish, close the elevated CMD prompt and also rebegin your computer system. Once the following startup sequence is finish, open up File Explorer and also double-click on the affected drive aacquire to check out if the worry has actually been resolved.If you’re still encountering the ‘There was a problem founding ~. The mentioned module could not be found‘ error, move down to the next potential deal with below.Method 2: Deleting autorun.inf secrets through Registry EditorIf you’re not comfortable through making use of a terminal to delete the problematic autorun.inf documents or multiple drives are influenced and also you want to fix the problem as a whole, a better method to carry out it is by means of Registry Editor.By utilizing Registry Editor to navigate to the area of eincredibly saved Run and also RunOnce vital, you can properly disable the autorun.inf papers that can be triggering the ‘There was a trouble founding ~. The specified module might not be found‘ error.There are four different places in the Regisattempt where the autorun.inf documents might be discovered. Using Regisattempt Editor, you have the right to acquire to each area manually and rerelocate the Run and also RunOnce keys that are permitting the autorun.inf file from denying you access to the drive.Here’s a quick overview on how to execute this:Note: The steps listed below are global and can be followed on Windows 7, Windows 8.1 and also Windows 10.Press Windows key + R to open up up a Run dialog box. Inside the recently showed up text box, form ‘regedit’ and press Enter to open up the Regisattempt Editor. When you check out the UAC (User Account Control) prompt, click Yes to provide admin accessibility.See more: Regsvr32 Exe Virus Removal Tool, How To Remove The Regsvr32Running the Regisattempt EditorOnce you’re inside the Regisattempt Editor, use the left-hand also side to navigate to the adhering to location:HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRunNote: You have the right to either navigate tbelow manually or you deserve to paste the place straight into the navigation bar and also push Enter to get tbelow instantly.After you manage to arrive to the correct location, move over to the right-hand also side and look for any kind of enattempt that doesn’t lead earlier to a well-known routine that you willingly installed. Be certain to look at the area (Data) to check out if this list has evidence of a PuP (Potentially unwanted Program) or remnants of a malware regime.Investigating for the corrupt Run or RunOnce keyNote: Ignore the (Default) enattempt.In instance you regulate to uncover evidence of a malicious Run vital, right-click it and also select Delete from the recently appeared context menu.Deleting the problematic keyNext off, it’s time to encertain that the rest of the staying Run and RunOnce areas don’t contain the very same attach to the problematic autorun.inf file. To do this, navigate to each of the following locations and repeat step 3 and 4 through all of them till eincredibly potential problem-causing crucial is deleted:HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRunOnceHKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRunHKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRunOnceAfter eexceptionally crucial has been deleted, close Registry Editor and also restart your computer. Once the next startup is complete, attempt to accessibility the drive aacquire and also watch if the problem is now readdressed.If you’re still encountering the ‘Tbelow was a difficulty founding ~. The mentioned module might not be found‘ error as soon as trying to accessibility it, move dvery own to the next potential fix.Method 3: Running CHKDSKAnvarious other potential culprit that could cause the apparition of this worry is corrupted data on your HDD. If this is the primary culprit behind the worry, you can most likely obtain the problem solved by running the CHKDSK utility.Some users that we’re additionally taking care of the exact same problem have reported that the ‘There was a difficulty starting ~. The mentioned module could not be found‘ error no longer showed up when they accessed their driver after running an Automatic CHKDSK shave the right to via the ‘Scan for and attempt recoextremely of bad sectors’ checkbox permitted.Here’s a step-by-action overview on running the CHKDSK utility to resolve corrupted information.Method 4: Running a malware scanIf namong the approaches above have actually enabled you to deal with the worry, it’s also feasible that the concern is being caused by an ongoing protection infection. If you haven’t done it yet, we extremely recommend that you percreate a deep shave the right to with a knowledgeable AV suite.If you already pay for a premium AV subscription, usage it to scan for any kind of malware that might still be lingering on your computer system.But if you’re trying to find a competent AV suite that is capable of identifying and also rerelocating any kind of remnant records that can still cause problems, you must think about making use of Malwarebytes.In case you need help triggering a deep sdeserve to via Malwarebytes, right here are some step by step instructions.Method 5: Refreshing every OS componentIf namong the potential fixes over have actually aided you accessibility your drive, it’s exceptionally most likely that the trouble occurs because of some form of device file corruption.In order to relocation eexceptionally Windows component without affecting your individual papers, think about doing a repair install.See more: Shockwave Flash Player Crashing Windows 10 Crash Since, Windows 10S And FlashIn situation that’s not a opportunity, the only viable settle as this point is to go for a clean install.