Forum Discussion
Server 2012 R2, C:\Windows\Installer at 137 GB and counting
Server 2012 R2, patched to current --
C:\Windows\Installer\ grew 18 GB in under a month, and by slightly less than that each of the two previous months.
We have drive space to throw at that folder (for now), but I'd like to put an end to this.
What's happening and how do I stop it?
Thanks,
I found the problem / solution --
I looked at the details of the files that kept appearing and found --
.MSI file
Title: Installation Database
Subject: Microsoft Azure AD Connect Upgrader
Author: Microsoft CorporationAzure AD Connect had Automatic upgrade enabled and these were the files that, presumably would upgrade me to 2.0.
However, the server is running 2012 R2, which does not support Azure AD Connect 2.X
There must have been some error loop that happened -- upgrade files download, install attempted, install failed, and instead of deleting the unneeded .msi files, Windows just downloaded a new one, four times a day.
I disabled Automatic upgrade for Azure AD Connect and stopped getting new .msi files.
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-install-automatic-upgrade
8 Replies
I found the problem / solution --
I looked at the details of the files that kept appearing and found --
.MSI file
Title: Installation Database
Subject: Microsoft Azure AD Connect Upgrader
Author: Microsoft CorporationAzure AD Connect had Automatic upgrade enabled and these were the files that, presumably would upgrade me to 2.0.
However, the server is running 2012 R2, which does not support Azure AD Connect 2.X
There must have been some error loop that happened -- upgrade files download, install attempted, install failed, and instead of deleting the unneeded .msi files, Windows just downloaded a new one, four times a day.
I disabled Automatic upgrade for Azure AD Connect and stopped getting new .msi files.
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-install-automatic-upgradeAbsolutely spot on, I was having exactly the same issue (120.7gb here). We are due to bin Server 2012 off this year (obviously) but we would have run out of space before that.....
- Just an update --
Still no solution.
C:\Windows\Installer\ grew 29 GB since my last post, about a month ago. I saw that post, and was hoping that MS had come up with an actual, legitimate solution in the past 10 years.
C: is now 173 GB total, with 137 of that in C:\Windows\Installer.
I could live with C: continuing to be at its current size, but eventually I'm going to run out of space on that datastore. I have other servers where this is not happening, so what's gone awry on this particular server?
