00:00Hey everyone and welcome back to the channel. Today, we're tackling one of the most frustrating
00:04errors any Windows user can face. You know the one I'm talking about. You've just installed a
00:10new game or a piece of software you're excited to try. You double-click the icon and boom.
00:15First things first, let's talk about what these DLL files even are. DLL stands for a dynamic link
00:21library. Think of them as shared toolboxes. Instead of every single program having its
00:27own complete set of tools, like its own hammer, screwdriver, and wrench. Windows lets them share
00:34a common set of tools. These are the DLLs. They contain code and data that multiple programs can
00:39use at the same time. This is super efficient. It saves disk space and memory. The files we mentioned
00:45earlier, like msvcp-140.dll and vcruntime-140.dll, are part of a package called the Microsoft Visual
00:53C++. This is a massive toolbox that thousands of games and applications rely on. When a developer
00:59builds their app using Microsoft's tools, they assume you have these common files on
01:04your system. The problem is, sometimes they're not installed, or you have an older version,
01:10or a file gets corrupted. That's when the error pops up. So, the logical first step isn't to go
01:17hunting for individual DLL files online, which, by the way, can be very risky. Instead, we're going
01:24to install the entire official toolbox directly from the source. This brings us to our first and
01:29most effective fix, the Visual C++ redistributable runtimes all in one package. This is the holy
01:36grail for fixing DLL errors. Some incredibly smart people in the tech community have created a single
01:41convenient installer that bundles every version of the Visual C++ redistributable you could ever
01:47possibly need, from the old 2005 versions to the very latest ones. This one package can solve about
01:5490% of all DLL-related issues. Let me show you how to get it. First, open up your web
02:01browser and
02:02search for Visual C++ redistributable runtimes, all in one tech. TechPowerUp is a trusted site for this
02:09kind of utility. Once you're on the page, you'll see a download link. Go ahead and click that to
02:16download the file. It'll come as a zip archive. Once it's downloaded, you'll need to extract it.
02:22Just right-click on the downloaded file and choose Extract All. This will create a new folder with the
02:28installer inside. Now, here's the most important part. Navigate into that new folder. Find the file
02:35named Install Underscore All. BAT. Right-click on it. And this is Crucial Select. Run as Administrator.
02:43Your screen might dim, and a user account control prompt will ask if you want to allow this app to
02:48make changes.
02:50Click Yes. You'll then see a series of black command prompt windows appear. Don't be alarmed.
02:56This is the script working its magic. It's automatically and silently installing every
03:01single version of the C++ package, both the 32-bit x86 versions and the 64-bit by 64 versions.
03:08It's methodically filling in every gap in your system's library. Just let it run. It might take
03:14a few minutes. So be patient. You'll see the windows pop up and disappear as it completes each installation.
03:20Once all the windows are gone and the process is finished, the single most important final step is to
03:26restart your computer. A restart ensures that Windows and all your applications properly recognize the new files.
03:32Once your PC's back up, try running the program that was giving you the error. In most cases, it will
03:38now
03:38launch perfectly, and your problem will be solved. So, what if the L-in-1 package didn't work, or you're
03:46dealing with a different kind of system file error? This brings us to our second powerful tool,
03:51the system file checker, or SFC. This is a utility built right into Windows that S designed to scan
03:58for and repair corrupted or missing system files. The DLL that's causing your problem might be a core
04:03Windows file that got damaged. And if that's the case, SFC is your best friend. To run it, you need
04:10to
04:10open an elevated command prompt. To do that, click on your start menu and type C. You'll see
04:15command prompt appear in the results. Don't just click on it. Instead, right-click on it, and select
04:22run as administrator. Again, you'll need to approve the user account control prompt by clicking yes. Now, you'll
04:29have a black window with administrative privileges. Inside this window, you're going to type one simple
04:35command. SFC, a space, a forward slash, and then scano. That's SFC, space, slash, S-C-A-N-N-O
04:46-W.
04:48Now, press enter. The system file checker will now begin a thorough scan of your entire operating
04:54system. It's comparing your current system files against a cached, known good copy that Windows keeps
05:00for exactly this purpose. This process can take a while. Anywhere from 5 to 15 minutes, depending on
05:07the speed of your computer. You'll see a percentage counter, letting you know its progress. Just let
05:12it do its thing. Once the scan is complete, it will give you one of a few messages. The best
05:17case
05:17scenario is Windows Resource Protection did not find any integrity violations. This means your core
05:23system files are all okay. If it says Windows Resource Protection found corrupt files and successfully
05:29repaired them, that's great news. It found a problem and fixed it. In this case, you should restart your
05:35computer and then try your program again. Occasionally, it might say it found corrupt files, but was unable
05:41to fix some of them. If you get that message, don't worry. We still have options. But for now, let's
05:48assume
05:48the scan completes. Remember to restart your PC afterwards to apply any repairs it might have made.
05:54Alright, let's move on to a more advanced surgical technique. This is for those rare cases where the
06:00previous methods haven't worked, or you're dealing with a very specific, stubborn DLL that just won't
06:06cooperate. This method is manual DLL registration using a command called regsor32. What does that mean?
06:13Sometimes, a DLL file can exist on your computer in the correct folder, but Windows has somehow forgotten
06:20about it. Its registration entry in the Windows registry is either missing or corrupt. The regsor32
06:25command essentially reintroduces the file to Windows, telling the operating system,
06:30Hey, this file is here, and this is what it does. It re-registers the file so other programs can
06:37find
06:38and use it. A word of caution. This won't work for all DLLs. Many modern DLLs, especially the C++ runtime
06:46files we discussed, are not designed to be registered this way. This method is typically for older DLLs,
06:53or specific component object model files. But if you're out of options, it's worth a shot.
06:59Let's say for example, the error message specifically names a file like some underscore funky underscore file.
07:05D, D, D. The first step would be to make sure that file is actually in the right place,
07:11which is usually either the system32 folder for 64-bit files, or the cswow64 folder for 32-bit files
07:20on a 64-bit system. Let's assume the file is present, just like with the SFC scan. You'll need to
07:27open
07:28command prompt as an administrator. Right-click the start menu, find command prompt, and run as
07:34administrator. Now, in the command prompt window, ULL type regsver32, followed by a space on the full
07:41name of the file you want to register. So, it would look like this. Regsver32, some underscore funky
07:48underscore file. D, daily. After you type that, press enter. If it works, you'll see a pop-up message
07:58saying, loregasterver, and some underscore funky underscore file. There, yeah, succeeded. This
08:04means you've successfully registered the file. If you get an error message, it likely means the file
08:09isn't meant to be registered this way, or it has other dependencies that are missing. After a successful
08:14registration, it's a good idea to restart your computer before trying to launch your program
08:18again. This is a more targeted fix, but when it works, it feels like magic. To wrap things up,
08:24we've covered the three most effective methods for fixing those dreaded DLL not-found errors.
08:29We started with the powerhouse solution, the Visual C++ all-in-one package, which solves the vast
08:35majority of these problems by installing all the necessary runtimes your programs need. If that
08:40doesn't do the trick, we moved on to the system file checker, SFC Scano, a built-in Windows tool that
08:46repairs your core operating system files. And finally, for those really specific and stubborn cases,
08:53we learned how to manually register a DLL using the regsver32 command. By following these steps in
08:59order, from easiest to most advanced, you should be able to resolve almost any DLL issue you encounter.
09:06The key takeaway is to avoid downloading single DLL files from shady websites.
09:11That's a recipe for disaster. Always go for the official, complete packages, or use the trusted
09:17tools built into Windows itself. Your system will be more stable and secure for it.
09:21I really hope this guide was helpful in gotcha games and applications up and running again.
09:26If it did, please consider hitting that. Like button, it really helps the channel out.
09:31And if you want to see more tech tips and tutorials like this one, make sure to subscribe so you
09:35don't
09:35miss out. If you have any questions or ran into a particularly tricky error, drop a comment down below,
09:41and I'll do my best to help. Thanks so much for watching, and I'll see you in the next video.
09:45See you next time.
Comments