[Vmware Installation Error Microsoft Runtime Dll
Kody Coste
Note: VMware Tools 10.3.0 is deprecated due to a VMXNET3 driver related issue. For more information, see KB 57796. Install or Upgrade to VMware Tools 10.3.2 or higher versions of VMware Tools. This deprecation does not impact 10.3.0 open-vm-tools.
Installing or upgrading to VMware Tools 10.3.0 is not supported for Windows versions that do not meet the prerequisites. Users are recommended to use VMware Tools 10.2.x or older until Windows OS is updated to meet the prerequisites for VMware Tools 10.3.0.
VMware Tools ISO images are frozen for some end of life guest operating systems. Some ISO images are not included with ESXi in the tools-light VIB. For more details, see the VMware Tools Documentation page. All VMware Tools ISO images are available for download from
VMware Tools for Windows: 32-bit and 64-bit installer executable (.exe) files are available for download. These files are provided for easier access and installation of VMware Tools in Windows guest operating systems.
When a newer version of vmtoolspkg VIB is installed, VMware Tools status might not change. This limitation is observed in vSphere 5.5.x and update releases. To work around, power off and power on the VM or reboot the host.
Resolution on incompatibility and general guidelines: While upgrading ESXi hosts to ESXi 5.5 Update 3b or ESXi 6.0 Update 1 or later, and using older versions of Horizon View Agent, refer to the knowledge base articles:
The Windows pre-Vista iso image for VMWare Tools is no longer packaged with ESXi. The Windows pre-Vista iso image is available for download by users who require it. For download information, see the Product Download page.
The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware Products. The VMware Product Interoperability Matrix of VMware Tools 10.3.0 can be applied to VMware Tools 10.3.2.
The steps to install VMware Tools vary depending on your VMware product and the guest operating system you have installed. For general steps to install VMware Tools in most VMware products, see General VMware Tools installation instructions (1014294).To set up productLocker to point to the shared datastore, see KB 2004018.
For specific instructions to install, upgrade, and configure VMware Tools, see the VMware Tools Documentation page.
On Linux and UNIX like operating systems, the process ID (PID) of a stopped VMware Tools service might get reused immediately by the system. As a result, the new process might get canceled by the VMware Tools service init script.
Prior to VMware Tools 10.3.0, gathering network adapter information in a Linux guest OS with many IPv6 routes was a time-consuming process with 100% use of the CPU of a core. The exported data contained only a maximum of 100 routes. IPv4 routes took precedence over IPv6, leading to data loss in reporting IPv6 routes. If there were more than 100 IPv4 routes, IPv6 routes were not reported.
When the package "libvmtools0" is installed in SUSE Linux 12 and open-vm-tools is not installed, the VMware Tools installer fails. This is set to prevent an incomplete installation. Users have to uninstall both open-vm-tools and libvmtools0 to install VMware Tools.
The Windows OS component Local Security Authority (LSA), which includes the Local Security Authority Server Service (LSASS) process, validates users for local and remote sign-ins and enforces local security policies.
The Windows operating system provides additional protection for the LSA to prevent security attacks. When this feature is enabled, any LSA plugin must be signed with the file signing service for Local Security Authority (LSA). VMware Tools installs an LSA plugin called vmwsu_v1_0.dllwhich is not signed in the required manner and fails to load when RunAsPPL is enabled in LSA configuration. An error message similar to the following is displayed.
While installing VMware Tools by running the setup command, a dialog box appears which displays a progress bar. This dialog box displays the progress of the installation of the VC 2017 redistributable package which is used by VMware Tools. The VC 2017 redistributable package installation does not complete, preventing the launch of the general VMware Tools installation dialog box.
The issue is observed with Windows Vista Service Pack 2 operating system which has Microsoft Document Explorer 2008 package installed when VMware Tools installs the Microsoft VC 2017 redistributable package.
When you have a secure boot VM with Microsoft Hyper-V and virtualization-based security enabled with Device Guard and Code Integrity policy set to enforced, then drivers, glxgi, pvscsi, vsepflt, and vsock might generate the event log warnings similar to the following.
Description:
Code Integrity determined kernel module system32\DRIVERS\vsock.sys that did not meet the WHQL requirements is loaded into the system.
Check with the publisher to see if a WHQL compliant kernel module is available.
Installing or upgrading of VMware Tools to 10.3.0 fails on Windows if operating system pre-requisites are not met, or the VMware Tools dependency on Microsoft VC runtime package cannot upgrade without a system reboot. A dialog box is displayed to the user which specifies the URL to a knowledge base article. This article cannot be accessed by clicking the link directly.
"The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'vc_runtimeMinimum_x86.msi' in the box below."
I'd like to be able to solve this problem without having to do a re-installation of the OS. So far, I've tried /sfc scannow, repairing through the Visual Studio Installer, and reinstalling the C++ redistributables, but all too no avail.
I ran into this problem as well on a recent build of Win 10 + trying to install latest VS Community. When I entered this state, things appeared to be super broken. Here's the sequence of events that I took which finally worked:
There are usually the "Minimum runtime" and the "Additional runtime"-components. After I've uninstalled both of them with this tool, I could just install a programm that uses these runtimes (for example Visual Studio) and it would download and install the missing features, after that, everything workes perfect for me.
Then use the Download troubleshooter and choose to Uninstall the item mentioned. When hovering on the list of items, make sure the GUID shown matches the GUID in the error shown, e.g.
I have a ImageFORMULA P-215 Scan-tini scanner which worked without any problems with my Lenovo X230 laptop running Windows 7 64-bit. However, I have been unable to get the CaptureOn Touch software to work on my Asus Transformer TA100T notebook running Windows 8.1 32-bit. The software and driver installation completed without any errors (without the scanner connected). But when I connect the scanner into the USB port and run the Capture On Touch software, it always comes up with a Microsoft Visual C++ runtime library error - Program C:\Program Files\Canon Electronics\P215\TouchDR.exe abnormal program termination.
thx,so we know that some windows or redist update breaks touchdr.exe, doing a clean install however is not an option for me, it takes days to configure all the other software, so why not fix the issue with touchdr.exe?
I might seem annoyed, but I have several canon scanners that has become unusable due to this issue, and I believe it is time for canon to provide a workable solution?
best regards Thue.
The last step would have been, reproducing the failure while a log-software is running. However, to reset all log files in my ->Temp-Folder I decided to delete ALL my temporary data on my Computer. I used the Windows10 settings app for that (System->Storage->TemporaryFiles). All of a sudden, the scanner worked afterwards nicely with the CaputureOneTouch. It still doesn't work with the Windows10 scanner app, but that doesn't bother me.
You can verify the timing by leaving the scanner disconnected until CaptureOnTouch V4 is running. Once you plug in the scanner, the app will crash. However, it is NOT a driver error. The scanner is working well all the time with other Twain-compatible apps. It is still the TouchDR.exe, which is causing the problems.
I tried so many things, other drivers and the standalone-software instead of the one from the scanner. All to no avail.
The canon-support was unable or unwilled to help as well. It's ridiculous that such a big company cannot provide a reliable driver and just ignores that a lot of people cannot use their device as they used to.
I've ran into this issue multiple times now. It works when starting with a clean installation of windows but you must not forget to install the scanner drivers and software at first because there seems to be an order issue? It is really annoying if you forget to install and test the scanner is working and find out after a week the same issue is back and you can start all over again because it seems unfixable. Also tried other scansoftware (Vuescan), which does work, but I personally find the captureontouch better/easier.
For now I have found a workarround by using vmware player. I've created a clean Windows installation on which I only installed the drivers and the software and everything is working now. I also disabled the networkcard to prevent any windows update from spoiling it. Just to be sure So if i want to scan I just power on the image and when done, hibernate it so it ready to go when needed. The scanned files i then can move to my own windows.
Now the trick here is that with the current configuration, all these logical CPUs are accessible for both TwinCAT and Windows. Because they are accesible to both Windows and TwinCAT they need to be shared (through some magic done in TwinCAT). What we need to make sure is that TwinCAT has 100% access to at least one CPU-core. Now I should mention that TwinCAT generally is not too fond of having hyperthreading enabled, so I would suggest to disable it (possible in the BIOS/UEFI of most computers), though I for this example will not do so. If hyperthreading would be disabled the above would show just four rows, one for each physical core. Change the above settings so that we have 1 isolated core and 7 cores for Windows like this:
795a8134c1