installation problem - ControlService/KmdUtil [SOLVED]

[Craig@Invincea]

I already ran that PowerShell command and e-mailed you the TXT file as you requested the other day. A few posts up, you said "Thanks. Let me take a look at it this morning." Did you not get that e-mail after all?

I will look for and post the additional events tonight. Thank you for your help!

Yes, we looked at it. I noted this in my post on THU DEC 10 @ 1501.

There is nothing there that would indicate any issues. But again, that just shows up programs you have running and may give an idea of something conflicting (such as AV). If you want to run a procmon, that's more of a test. Something installed on your machine is blocking the driver. That's all we can say. It's not a SBIE issue as far as we can tell.

Is this a portable installation of SBIE?

Something is there on your machine blocking the driver.

Get procmon here (free) https://technet.microsoft.com/en-us/sys ... 96645.aspx

Step #1
Close any programs that are not needed.
Run Procom (not sandboxed)
Start to install SBIE.
Install SBIE with the "run browser sandboxied" shortcut
Let the error happen/not load/etc
stop capturing events in Procmon (under file)
then Save the results (under file, make sure "save all events it ticked") and
save in PML format.
These files can be large, so post somewhere we can download and look (link)
OR (Please zip them!) and send to Support@sandboxie.com

[mooop12]

Any word on this? I'm experiencing the same issue. Running Windows 10 64-bit. Tried both the regular version and the beta version of Sandboxie. The weird thing is that the service says it has timed out after 30 seconds but the error shows immediately not after 30 seconds, same thing in event viewer. Also tried increasing timeout period to 180 seconds, didn't help.

[Craig@Invincea]

Any word on this? I'm experiencing the same issue. Running Windows 10 64-bit. Tried both the regular version and the beta version of Sandboxie. The weird thing is that the service says it has timed out after 30 seconds but the error shows immediately not after 30 seconds, same thing in event viewer. Also tried increasing timeout period to 180 seconds, didn't help.

Are you running the portable version of Sandboxie? We've haven't had any other reports other than this last one - and the only on for a long time, for which it was last updated in Early December with no more information from that user. Did you try any of the steps there? If the driver won't install, it's usually something on the host that may be blocking installation. Antivirus? Antimaleware? etc. Confirm the Sandboxie Service is running or not?

[mooop12]

Found a fix. There seems to be an ongoing unreported Windows bug at least since Windows 7 where Visual C++ Redistributable package doesn't install properly and the system tries to load 32-bit libraries instead of 64-bit versions. This was the case here, manually extracting msvcr100.dll from the Visual C++ 2010 x64 package and putting it in Sandboxie directory fixes the problem.

[Craig@Invincea]

Found a fix. There seems to be an ongoing unreported Windows bug at least since Windows 7 where Visual C++ Redistributable package doesn't install properly and the system tries to load 32-bit libraries instead of 64-bit versions. This was the case here, manually extracting msvcr100.dll from the Visual C++ 2010 x64 package and putting it in Sandboxie directory fixes the problem.

Sandboxie doesn't check for 32/64 bit. It just looks to see if it's installed. Any C++ installs or updates recently?

[mooop12]

It's a practically new Windows install. And Sandboxie doesn't have anything to do with it. In System32 there is a 32-bit msvcr100.dll when it should be 64-bit, the redistributable installer is bugged though it doesn't seem to be common but it is an old bug. You can either replace it directly in System32 or add a proper dll to where the executable is.

[PortablesFan]

Sorry for the long delay; some significant IRL events have been going on...

I just e-mailed Sandboxie Support a download link for the requested file, and will try the solution posted by mooop12 in the meantime.

[PortablesFan]

Craig, I didn't notice/remember that you had asked whether I was running the portable version. Do you mean Wraithdu's old wrapper? I used to way back when, but not now, and never on the PC in question.

mooop12, you solved my problem!!! If you happen to see this thread again--how did you ever track it down on your system? How did you find out about this "unreported bug"? I have a somewhat computer-related job with no formal training, so I'm always on the lookout to learn something new...

**************************

For anyone else in the future having a similar problem, mooop12's solution worked, but I had to figure out how to do it by some trial-and-error and further web searching. I will outline what helped me...

1) Downloaded Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) from the Official Microsoft Download Center page:
https://www.microsoft.com/en-us/downloa ... x?id=13523

2) Followed the instructions on this page to get at the files:
http://www.tomshardware.com/answers/id- ... 64bit.html

3a) Once you grab the set of files that were inside of the downloaded EXE, look for vc_red.cab (if you have File Extensions set to display in Windows Explorer) You can delete all other files.

3b) The tutorial on TomsHardware assumes the use of WinRAR, which I do not have. Instead, I used Universal Extractor:
http://www.lupopensuite.com/db/universalextractor.htm
(The above is an unofficial but authorized portable version in a self-extracting .EXE archive, and is my recommendation. If you'd feel safer with a download from one of the 'main' sites, use the following for the 'installer' version from Softpedia.)
http://www.softpedia.com/get/Compressio ... ctor.shtml

3c) It turns out you can also drill straight down into the .CAB file in Windows Explorer on Windows 7.

4) However you get into vc_red.cab or get files out of it, follow the rest of the instructions on the TomsHardware page: look for a file called F_CENTRAL_msvcr100_x64 and rename it to Msvcr100.dll

5) I already had a previously failed installation of Sandboxie in Program Files [not x86], so I simply copied my brand new Msvcr100.dll file into C:\Program Files\Sandboxie

6) Instant success--huzzah! I was able to start a program in Sandboxie!

**************************

I recognize that this particular issue has affected very, very few of us so far (that we know about), but Sandboxie might want to include some kind of error check in its installer for the proper Msvcr100.dll to prevent future potential users from throwing their hands up in despair/disgust and just walking away from the product. (I'm a long-time user, so...I was missing it on this PC!)

[Craig@Invincea]

SBIE just checks if it's installed, not for a particular version.

[mooop12]

This issue I've been having for at least a few years now. It started I think when I tried to run Office 2010 on Windows 7, it was throwing errors for which the cause happened to be the missing dll. Usually you get an error like "0xc000007b" but not in the case of Sandboxie, here I thought of using a dependency walker on sbiesvc.exe which pointed out the 32-bit dll. A few of the bigger companies, like that one brand responsible for the most popular PDF reader, are aware of this issue since they post the same solution in their official help sections.

Are you by any chance running a non-english Windows install? This might sound stupid but since the issue applies even to new Windows installs the only thing I can think of is that it's because of running another Windows language.

[PortablesFan]

Nope, I think it's an English install. (pre-installed on an Acer laptop)
I assume yours may be non-English, then, as part of the basis of your theory?

[mooop12]

Well then I'm out of ideas. It's funny because the first time it happened I was running a completely different set of hardware and it was on Win 7, and yet now after these few years I still have this issue every time I reinstall my system.

[Craig@Invincea]

I'm curious, try Curts suggestion on this older thread if you can http://forums.sandboxie.com/phpBB3/view ... 00#p111255

[mooop12]

I'm assuming it was about forcing VC++ redist to fix the file. Yes, removing those files manually and then using VC++ redist again fixes the issue, the redist install places proper x64 dll in system32.

[Tester100]

I'm curious, try Curts suggestion on this older thread if you can http://forums.sandboxie.com/phpBB3/view ... 00#p111255

I just had the problem mentioned in this thread with a Windows 10 installation, only a few programs like MSI Afterburner are installed. Deleting the MSVCR files mentioned in your linked thread helped me to fix the problem, thanks a lot!