Tag Info

Hot answers tagged

6

Looks like update KB3004394 is bugged in Windows 7 (fine in Windows 8): https://www.virtualbox.org/ticket/13677 https://forums.virtualbox.org/viewtopic.php?f=6&t=65056 https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/windows-update-kb3004394-issues/ace25277-7f65-4486-bc44-c1b106907a18 You can temporarily work around this by ...


5

It would seem that your program is 32-bit, but didn't install its needed 32-bit libraries on your 64-bit OS. MSVCP100.dll, is part of the Microsoft Visual C++ runtime libraries, so ensure you install the 32-bit versions of those C++ runtime libraries. You can get them from Microsoft here: Microsoft Visual C++ 2010 Redistributable Package (x86) You may ...


4

The correct course of action here is, as you say, not to go downloading random dll files from all of the internet but instead work out just which Visual C++ Runtime your program is expecting and install that. Chances are if it is Explorer that is complaining then it is because a new shell extension or related program is trying to work through it. You can ...


4

To repair use the following command at a command prompt (with privileges) DISM /Online /Cleanup-Image /RestoreHealth RestoreHealth: This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish ...


3

The threat of a DLL would be if gets executed by an executable. But if you download a malicious DLL, there are several ways it can get executed at the request of a non-malicious executable. You don't want a malicious DLL sitting on your machine. For example, you probably have several executables on your machine right now that will happily load and execute ...


2

I manually copied the corrupt file from a different computer with the same Windows installation. It took some permission changing, but I managed to replace the file.


2

Explanations Like you said, they did not update it when they ported the drivers to Windows 8. That said, it’s also possible (possibly even likely) that they chose to remove it from the Windows 8 driver because of a bug and/or incompatibility with Windows 8 and/or due to Windows 8’s different interface design (you normally don’t see the notification-area ...


1

Analysis I don't have the same hardware nor I use Windows 8.x, so what I'm going to provide is some static analysis. Strings At first I scanned the 64-bit mvs91xx.dll library file using the Strings utility. Strings just scans the file you pass it for UNICODE (or ASCII) strings of a default length of 3 or more UNICODE (or ASCII) characters. ...


1

From the message "The Ordinal 325 could not be located in the dynamic link library SHDOCVW.dll", it is possible that this DLL is corrupted, so maybe other system DLLs as well. Try sfc /scannow to see if it finds anything. If it does, you will need an XP SP3 boot CD to correct the errors.


1

Looks like your IE is broken from the shdocvw.dll error reported by NotePad. You can reinstall the current Windows service pack or upgrade your IE version to get IE-related files to a good state. Suggested reading: How to repair or reinstall Internet Explorer in Windows


1

The biggest problem with "Heartbleed bug" will be on the server side (websites). Though clients are affected too, it is much less possible that someone will misuse that. You can use Indy original SSL distribution from http://indy.fulgan.com/SSL/ You can find "openssl-1.0.1g" here which are the latest and fixed libraries. It should be fully compatible with ...


1

the regsvr32 located in SysWow64 folder is for 32bit dll It's a strange naming from microsoft: WOW64 means "windows [32bit] on windows 64bit" the one located in system32 is for 64bit dlls.


1

I had the same issue and all of provided instructions did not work. What worked for me is to finish all the updates.


1

Consider That The Originals May Have Been All Zeros It simply may be a misconception. Please look at other dll's and see if has happened to all of them or has happened in some certain situations. dll's are simply files and so will be treated the same. also look to see if some restoration isn't still in progress or something weird like that because it may ...


1

Should be fine, except you should force it into the SFC repository (WinSxS) and then let SFC put it back where it should go (the "file not found" error is SFC telling you it can't find the known-good copy in the repository when trying to replace the one missing from System32).


1

Since I just started to use windows 7 on my laptop, I don't know much... but I had a problem with the windows activation, so my windows crashed... and there was a way to fix it with the windows 7 installer (boot) dvd. I think that could be also useful to fix that "missing lpk.dll" problem: Just put in the dvd and reset the laptop, then boot from the dvd ...


1

ExplorerFrame mostly contains resources but all DLLs contain code that can be run by Windows; even resource-only DLLs contain code (that might by normally do nothing) that automatically runs when the DLL is loaded. It's part of how DLLs work on Windows. So you would have to make sure you are getting it from a trusted source, and even then you may have ...


1

You get it directly from zlib website. There's a link pointing to Windows prebuilt version: http://www.winimage.com/zLibDll.


1

First reaction: If your process is running on your machine, you could simply choose to not terminate it. If it's running on my machine, then it isn't your process, it's mine... and I will terminate it if I want to. The actual answer: Ultimately, no, there isn't. You can make it less easy by creating your process with a security descriptor that denies ...


1

Install the fix from this KB to resolve the issue with Update KB3004394: Install KB3024777 to fix an issue with KB3004394 on Windows 7 and Windows Server 2008 R2 http://support2.microsoft.com/kb/3024777/en-us



Only top voted, non community-wiki answers of a minimum length are eligible