I am building a couple of VM images using Packer (by HashiCorp) which calls an unattended file for the Windows Server (2012 R2 and 2016) configuration. That all works fine. Once the VM has been built the final call is made (by Packer) to a bat file which gets the VMware tools ISO and executes the setup64.exe with the silent switches. However, that install fails. The problem seems to be with installing the visual C++ runtime libraries. I get the standard 'Setup cannot continue. The Microsoft Runtime DLL insaller failed to complete installation' message in the installer log preceded by:Found "C:\VMwareTemp\GUIDSetup\vcredist_x86.exe"Cannot get short temp path for VC redist installerThe server auto logs on as local admin and UAC has also been disabled as part of the unattended script (for the purposes of troubleshooting). I have tried to manually install both the 32-bit and 64-bit 2008 SP1 C++ runtime installers as part of the unattended file (which install OK) before the script to install the tools is called but to no avail.Interestingly, if I can the same setup64.exe command after the VM has shutdown and been sysprepped, the command runs in OK and the tools get installed. So, is the error above in relation to permissions, possibly? I would be interested to hear anyone's thought, epsecially if you have come across the issue before!I will post in the VMware forums too as this may be nothing to do with the Server's OS at all.Cheers all,Dave.
>>That all works fine. Once the VM has been built the final call is made (by Packer) to a bat file which gets the VMware tools ISO and executes the setup64.exe with the silent switches. However, that install fails. The problem seems to be with installing the visual C++ runtime libraries. I get the standard 'Setup cannot continue. The Microsoft Runtime DLL insaller failed to complete installation'
vm tools microsoft runtime dll installer failed to complete installation
Turn off the VM, yes, turn off and wait for around 5 minutes, VM has to break all the open handles with parent host/vCenter. Turn on the VM and run VMWare Tools installer, this time the installation will complete without any error.
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.
I am using Windows 7 OS 64-bit and downloaded VMware server but when I try to install it shown the following error message when reach at 90%. The installation did not complete using Microsoft Runtime DLL installer. How can I overcome this problem? Have any idea? Any help would be appreciated. Thanks.
It is possible to name directories using characters that are not part of the system locale's code page. If such a directory is part of the installation path, then generic error 1722 occurs, and installation is not completed. Error 1722 is a Windows installer error code. It indicates that the installation process has failed. The exact reason for this error is not known at this time.
The following table contains a list of products that have unique installation behaviors.Product NameConsiderationsNotesAdobe Flash Player Removal ToolThis product only uninstalls ANY found version of Flash PlayerDeploy/Assign the uninstall of this tool in order to remove Flash PlayerAdobe Acrobat ProductsUpdates may fail to install with exit code 1612 or 0x8024002DThis is a known issue with Adobe Products. More information on Adobe's websitehere and here and Patch My PC's KB articleApple iCloudUpdates may fail to install if Apple Application Support (x86) is not installedInstall Apple Application Support (x86) before attempting to install iCloudApple iTunesApplication may fail to install if Bonjour of the same architecture is not installed.Install Bonjour with the same architecture as iTunes before installing iTunesThe code execution cannot proceed because dnssd.dll was not found. Reinstalling the program may fix this problem.AnyDesk MSIBase Install Only, Updates will not ApplyPatch My PC utilizes the Machine-Wide installer for AnyDesk MSI. The Machine-Wide installer uses the same MSI Product Code for all versions. This causes multiple issues concerning updates to the product as well as detection of new versions. Intune Updates will NOT apply.Bluebeam Revu 2020 and 2021Bluebeam 2020 and 2021 require a License be entered on the Command line for installation to complete.Add a Command Line using the right-click feature and ensure that: BB_SERIALNUMBER and BB_PRODUCTKEY are included.Cisco AnyConnect SuiteUnique Update BehaviorUpdate 2021-07-30: The logic from our applicability rules that would block install if the NAM Module is installed has been removed. If the NAM module is being used, we recommend using the script process to update AnyConnect specified here: Install Cisco AnyConnect Modules in a Specific OrderAt this time Updates to Cisco Anyconnect through the Software Update mechanisms will not occur if the Network Access Manager is installed. This behavior is in place to prevent loss of network connectivity, as the order of software update installation cannot be defined. The recommended workaround is to deploy updates through Base App installs in order to control the order of installation.Cisco AnyConnect Secure Mobility ClientUpdate may fail to install with certain right-click options.Selecting the right click option to block the application from starting during the installation under "Manage Conflicting Processes" may result in a 1603 error code and prevent other modules from installing.Cisco AnyConnect ModulesUnique Update BehaviorCisco AnyConnect Modules will not show as required until the Main Secure Mobility Client is installed. This is set in order to ensure the modules install after the main client. You can install all needed modules before the Secure Mobility Client in one update by following the optional customisation in this article: How to bundle Cisco AnyConnect modules to install in a specific order.Cisco WebexInstallation may fail on non-english Operating SystemsAdd the following to the command line to allow the installation to continue: ProductLanguage=1033Citrix WorkSpaceCustom commands require ; even if the proceeding setting is not configured.For setting STOREX configurations, 4 arguments are expected, Even if an argument is not provided, For example use the following format if only providing the first 2 arguments: STORE0="COMPANY; ;;"Dell Display Manager 2 or newerProduct requires .NET Core Desktop Runtime 5 installs.Product also does not uninstall 1.x.If the dependency is not installed before installing Dell Display Manager 2.x, the user will be prompted to download/install it.It is also by design for Dell's 2.0 installer to not remove older 1.x installs. Read more here.Java (JRE and JDK) Titled "Latest"Products with the word "Latest" in the title will always remove all previous versions and install the latest version available, this allows for easy upgrades for updates that are usually locked to a specific version.More informationMicrosoft Edge WebView2 (Uninstall)Uninstall will return an exit code 19 even when the uninstall happened successfully.Once the detection runs again, or the user tries to run the uninstall again the detection should validate the software removal and return a success status.Microsoft EdgeShortcuts may still be created with the "Delete Desktop Shortcut(s)..." right click option selectedUse the "Modify command line" right click option to add: DONOTCREATEDESKTOPSHORTCUT=trueMicrosoft TeamsBase Install Only, Updates will not ApplyPatch My PC utilizes the Machine-Wide installer for Microsoft Teams. The Machine-Wide installer uses the same MSI Product Code for all versions. This causes multiple issues concerning updates to the product as well as detection of new versions. Microsoft does not recommend updating the Teams MSI once installed (Microsoft Docs)Mimecast for OutlookBase Install Apps do not take Outlook bitness into consideration.Deploy the Base Install Apps based on the Outlook bitness not device bitnessNextcloudTrying to deploy a newer Intune Update of Nextcloud to a device with Nextcloud 3.1 or older installed will result in the update evaluating as not applicable.This is only an issue with Intune Updates, not SCCM or WSUS.Nextcloud stopped supplying an .exe installer after version 3.1 and now only provide .msi installers. The issue is that the .exe installer installed the 64bit app in 32bit locations in the registry on a 64bit system. As a result we can not differentiate between a pre-existing 32bit or 64bit install of Nextcloud on a 64bit system. We need to avoid inadvertently upgrading customers' product's architecture.To update from 3.1 to a newer version on a device in Intune, deploy the Intune App of Nextcloud to your devices. After your devices are off version 3.1 and are now installed using the .msi installer, moving forward you can use the software update of Nextcloud from the Intune Updates tab.Oracle VirtualBoxExpired Code singing certificate included in install may cause install to not completeOracle should update their code signing certificate to fix this issue. As a workaround, Patch My PC has created a script that can be used as a prescript to install the certificate: Link to Prescript on GitHubPuTTYUpdate will not show as applicable if version
The table below lists any known issues we are tracking.IssueDetected date or versionFixed date or versionStatusDell has Discontinued Dell Command Update (Classic) and is now only providing the Universal installer. Please move to the Dell Command Update for Windows Universal product within Patch My PC, and republish the App/Update if detection issues are found. Patch My PC will automatically migrate customers using these products to a new "Dell Command Update for Windows Universal" product with the next major release, 2.1.11.0, of the Patch My PC Publisher in December.11/29/20222.1.11.0FixedDell Command Update GUI is a UWP application that doesn't get installed at all during OSD, or if there is not a user logged on if you do it post-OSD.Dell support are aware, however please contact them to increase attention and awareness until a fix is released.11/29/2022N/AKnown issueLatest version of Autodesk Revit 2023 unavailable due to size. The cab file format that WSUS utilizes for updates has a maximum size of 2GB, and the latest Revit 2023 update is over 3GB.Vote or share your feedback on this feature request: Support products larger than 2GB.11/4/2022N/AKnown issueErrors May Occur installing Adobe Acrobat updates in Intune.Republish the ConfigMgr App, Intune App, or Intune Update and Sync to fix this issue.10/12/202210/12/2022FixedErrors may occur when deleting Intune Apps/Updates or gathering Intune Deployment Statistics when on GCC High (System.ObjectDisposedException)N/A2.1.6.35FixedTeamViewer is randomizing part of the download binary on every download of their .exe, causing a hash mismatch. Patch My PC is investigating workarounds.8/22/2022TeamViewer has rolled back the change on 9/08/2022FixedCustomers with the Publisher installed on Windows Server 2012 R2 or older, certain products may fail to download. PatchMyPC.log and alerts report "The request was aborted: Could not create SSL/TLS secure channel." This is because These web servers only allow particular TLS ciphers that are not supported in IE components for Windows Server 2012 R2 and older. Currently Affected Products Include:TechSmith Products, Tableau Products, and Cisco WebExWorkaround: manually download the installer for Snagit or Camtasia, store it in your Local Content Repository, and enable the option to Check the local content repository for content files before attempting to download content files from the internet. Patch My PC recommends upgrading from Server 2012R2 to a newer Windows Server version if possible, as we are seeing a trend of vendors moving their downloads to ciphers unsupported on Windows Server 2012R2N/AN/AKnown issueAuto-publishing rules configured for WSUS/ConfigMgr updates, with any custom options set in the dropdown beside it, will produce continuous alerts and log entries in PatchMyPC.log to republish the updates meeting the auto-publishing rule threshold.Workaround: Apply custom actions at the All Products or vendor level in the Updates tab. This will apply the custom actions to all child items including those not yet enabled. These will still be applied to child items automatically enabled by auto-publishing.1.5.1 or 1.8.02.0.5.0FixedWhen adding a single right-click option (Pre/Post Script, MST File, etc.) on ConfigMgr Apps, the content will be updated but the command line may not be updated accordingly.2.0.0.02.0.0.1FixedThe Patch My PC Publisher may attempt to revise an update on every sync. This occurs when an update has been republished twice, the Publisher checks the wrong revision for changes and attempts to change it every sync2.0.0.02.0.3.0FixedTeamViewer update may fail if the "Prevent the end-user from opening an application while the application is updating" is selected under "Manage Conflicting Processes"2.0.1.0N/AFixedAuto-enable feature of Intune Scanning may cause duplicate Win32 apps to be published within Intune. This would occur if some applications were found in an Intune scan, and a ConfigMgr scan.2.0.0.0FixedMSP-based products do not support most right-click custom actions due to WSUS applicability.1.0.0.02.1.11.2FixedZoom Meetings may upgrade to the newly released 64-bit version when the 32-bit version was installed, which may cause settings to revert to defaults. From 3/29/2021 to 4/1/2021, Patch My PC offered the 64-bit version of Zoom Meetings 5.6.1 in place of the 32-bit version of Zoom Meetings. If this update was synced and deployed during this time, 32-bit versions of Zoom Meetings would be upgraded to 64-bit versions, this does not break the functionality of the application but my revert settings to default.The 4/1/2021 catalog release replaced the 64-bit update with the proper 32 and 64 bit updates for Zoom Meetings, these updates now detect the architecture of Zoom Meetings that is installed and will install the appropriate version as applicable.5.6.1 (3/29/2021)5.6.1 (4/1/2021)FixedBug when selecting scopes: If a user attempts to set scopes at the Vendor or All Products level in ConfigMgr, upon closing and reopening the publisher, the App tree will not show any applications at all.2.0.3.02.0.4.0FixedAn error occurred while testing TCP port.: No connection could be made because the target machine actively refused it :80 [[System.Net.Sockets.SocketException]]2.0.3.02.0.4.1FixedThe Publisher will Publish an Intune Application, or Intune Update if found during a scan, despite being marked to 'Exclude from auto-publishing'2.0.0.02.0.4.2FixedSoftware may be marked for revision during every sync of the Publisher. This would occur when PreventConflictingProcessRestart was in use and the KillProcess was set instead of Notify.2.0.1.02.0.4.2FixedThe '...delay the in-place application upgrade by...' does not respect all configuration options such as 'Retain up to # previously created applications'Various2.0.8.2FixedUser Based ConfigMgr Applications may default to System Type installation in ConfigMgr.2.0.7.02.0.8.0FixedInteraction with the Manage Conflicting Process pop-up may not be possible if "Do not allow user deferral" option is set in Manage Conflicting Processes2.0.8.02.0.8.1FixedIntune apps and updates do not use the specified temp directory for downloads1.7.0.02.0.8.2FixedWebhook Option to send to Slack may be reverted to Teams upon opening the Patch My PC Publisher GUIWorkaround: When opening the Publisher and using Slack Webhooks, reset the option to Slack before saving and closing the Publisher.2.0.8.02.0.8.2FixedManage Conflicting Processes may fail to enumerate the blocking processes causing the UI to close, and kill the blocking process unexpectedly. 2.0.1.02.0.9.0FixedManage Role Scope tags will fail if a non-existent scope is associated with a ConfigMgr app.2.0.3.0FixedIntune assignment only allows a group to be specified once.1.7.0.02.1.6.35FixedThe 'Manage Conflicting Process' UI shows 'install' language instead of 'update' language when performing an Intune Update2.0.8.02.0.9.2FixedConfigMgr apps may have their content refreshed every sync if a PreCommandArg, UninstallPostCommandArg, or PostCommandArgUninstall are specified2.0.8.02.0.9.1FixedThe 'Prevent the end-user from opening an application while the application is updating' option when used with an Intune app or update may result in a 'Windows cannot access the specified device, path, or file....' error message.2.0.5.02.0.9.2FixedConfigMgr application may revise every sync.2.0.9.12.0.9.2FixedSome products published to WSUS report as failed installation from the clients, however the software is actually updated successfully on the client. This currently impacts Adobe Digital Editions, Nextcloud, and Dell Command Update for Windows. This is because in the catalogue custom defined success exit codes failed to publish correct to WSUS using the Publisher. These products used non-standard successful exit codes.Various2.0.9.2FixedIf 'Delay in-place upgrade' and 'App retention' are enabled for ConfigMgr apps you may see duplicate applications created2.0.1.42.1.0.1Fixed'Recreate Detection Script' does not populate the correct registry hive for User based apps in ConfigMgr2.0.8.02.1.0.1FixedApplication uninstallation may report failure if the uninstall process creates a child process causes ScriptRunner to exit prior to uninstallation completing1.02.1.0.1FixedPublisher may fail to properly parse product parameters which contain nested quotes causing continuous revisions or errors when parsing argumentsVarious2.1.0.1FixedWhen you republish an Intune application the icon is not set.2.1.0.12.1.1.1FixedOrganization Name is not set properly for ConfigMgr applications.2.1.0.02.1.1.1FixedWhen 'override manual assignment changes' is checked for an Intune product, and you have an 'exclude' assignment the Publisher will fail to process all assignments. 2.0.5.02.1.1.1Fixed"Republish" does not compare the hash of scripts and files for ConfigMgr2.1.1.02.1.1.1Fixed"Republish" may cause multiple republish operations for the same product to happen if used across multiple tabs.2.1.1.02.1.1.2FixedRequired deployments, including task sequence installs, of ConfigMgr Application for Adobe Acrobat Reader DC Continuous (x64) fail with exit code 150201. Clicking "retry" and available deployments succeed.Workaround: set the user experience option on the deployment type to "Allow users to view and interact with the program installation". Note that this workaround may not work to fix the application installing in a Task SequenceAdobe Acrobat Reader DC Continuous (x64)N/AKnown issueRepublishing an Intune application or Update which has existing assignments may cause the assignment to be deleted. It will be recreated during the following sync.2.1.1.02.1.3.0FixedThe "Delay in-place upgrade" feature is used for ConfigMgr applications the delay may be off by one day if the server is configured with certain timezones.Various2.1.3.0FixedManage Conflicting Processes may fail to launch if the 'First notification delayed +...' setting is used and the client device has a culture with a short-date format that is not parsable by the en-US datetime parse methodVarious2.1.3.0FixedRepublishing a ConfigMgr application removes application supersedence relationships.2.1.0.12.1.3.0FixedRepublishing a ConfigMgr application breaks the Manage Conflicting Process option to use 'ConfigMgr app max run time'2.1.0.12.1.3.0FixedManage ESP (Enrollment Status Page) within the Publisher throws a 403 forbidden error. AllAllFixedPowerShell Requirement Script for Adobe Acrobat Reader DC Continuous (en-US) fails to code sign properly. We are aware of and working to resolve this encoding issue.All2.1.6.2FixedPatch My PC tries to publish to Intune even if it is not configured, returning a message in the log similar to "Syncing: %3CEnterTenantDomainHere%3E..."2.1.4.02.1.5.0FixedPause does not account for postponed binaries. If there is an exist postponed binary it will publish even if a pause is set.2.1.4.02.1.5.0FixedScriptrunner may fail to find the uninstall string in the registry for some products.2.1.4.02.1.5.0FixedScriptrunner may fail to validate an installation after the installer completes causing a 3 minute delay after installation completes. 2.1.4.02.1.5.0FixedVersion will not be appended to retained ConfigMgr applications when 'Update existing application's metadata...' is set2.1.5.02.1.6.0FixedConfigMgr applications will fail to install with error code 0x80070057.2.1.6.352.1.8.0FixedIf an existing product has a new Patch My PC defined pre/post script added the Publisher will edit the command line, but not add the file to the package.Various2.1.11.0Fixed 2ff7e9595c
Comments