Check our other helpful areas that might answer your question

Hello,

It seems that Windows 10 KB4551762 breaks the installation process when installed on a shared location with Basic or Silent UI level.

Recently we’ve received some complaints from our users that they cannot install updates, be it a major upgrades or patches when the destination (install folder) is found on a shared location.

We have further investigated this behavior and we confirm this behavior. It seems that after Windows receives the KB4551762 update, once installed on a network location, the installed application cannot be uninstalled.

Since the upgrade means the uninstall of the old product version and the installation of the new product version, the upgrade process will fail as well.

Not just major upgrades are affected, it seems that you cannot install patches either.

During upgrade process, the following error occurs:
The problem does not occur if running the update or trigger the uninstall process from an elevated CMD. So, this issue seems to be related to the elevation process.

Once you trigger the major upgrade, or patch installation from an elevated CMD, everything works as expected, it doesn’t matter if the upgrade is made with Basic UI or Full UI.


Workaround:

• Remove the problematic KB4551762 update
• Elevate the CMD and trigger the update/uninstall from elevated CMD

I have come across this same issue with several MSI files that point to network locations. I have a ticket open with Microsoft but they don't seem to know what it is. I was wondering if you have come across a solution yet? The elevated command prompt fix doesn't work for my MSI's and I also push them via SCCM and that is broke as well since the kb4551762 update. If I get a resolution I will post it here.

Hi All,

We too have this issue with our installers over P2P, domain installs seem to be unaffected.

Dan do you have the Microsoft ticket number maybe having more people reported might give it a boost!

Thanks

My open ticket with Microsoft is 120032424005803. The vendor (FDOT) that supplies the MSI's I use are seeing the same exact issue on their end after the KB hit.

It's most likely a security change blocking MSI access to shared network locations. Microsoft is still investigating it.

Hello,

I have two customers, each with many (40) workstations where my product is installed, who still have this problem.

Using cmd with admin priviledges to install/uninstall doesn't solve the problem.

Is there any new info on a correction for this error?

Thank you,
clint

No luck, I've worked with Microsoft for a workaround for hours. KB4551762 on Windows 10-1903/1909 blocks install packages from accessing shared network locations.

https://support.microsoft.com/en-us/hel ... -kb4551762
Updates a Microsoft Server Message Block 3.1.1 protocol issue that provides shared access to files and printers.

I've had to recreate my SCCM packages to install to a temp location on C: then apply a system variable to point back to the network.

I haven't figured out the uninstall problem with the older packages. (I think I can change the network call out in the registry for the MSI somewhere but haven't looked into it yet as I rarely uninstall those packages)

Follow-up:

One of my customers changed the path in the registry to the folder which couldn't be removed (error 1315), and then the deinstallation worked.

The installation was created with AI 13.7.

The same customer then immediatedly installed an install program created with AI 16.9 in the same manner as with the 13.7 problem install program.
This install program was no different in settings or files than the one created with AI 13.7.

For testing, the customer then uninstalled the AI 16.9 program without any problems.

I also had several different customers who had problems installing the AI 13.7 installation on a W10 machine with a newer version.
Building that install program with AI 16.9 solved the problem.

clint

Hello,

Has there been any more development on this issue? It has been around three months when this issue was introduced. Is there any way we can get a timeline from Microsoft of a fix? Or some kind of workaround that can be done to allow patching to work?

The June cumulative update resolved the issue for me.

June 9, 2020—KB4560960 (OS Builds 18362.900 and 18363.900)

This security update includes quality improvements. Key changes include:
Addresses an issue that prevents users from updating .msi files from a network folder.

As per

by CaseyGrimes » Mon Jul 13, 2020 9:20 pm

The June cumulative update resolved the issue for me.

June 9, 2020—KB4560960 (OS Builds 18362.900 and 18363.900)

This security update includes quality improvements. Key changes include:
Addresses an issue that prevents users from updating .msi files from a network folder.

I can also confirm that our installers not also work as they used to after installing this windows build version.