Switching from Core to GUI fails after applying Windows updates

---

After installing Server 2012 R2 Core and fully patching with Windows Updates I tried to install the GUI and it failed. I found countless search results in Google with the same issue. This happens whether you install the GUI and try to change to Core or install Core and try to change to GUI. It works until you patch for the first time.

The fix seems to be to manually apply every update that is installed on your server to the install.wim file. Otherwise your server files are different than the source that the install-windowsfeature / uninstall-windowsfeature is looking at. Has anyone found an easy work around for this? There are a number of scripts I found in the search results but I am curious if Microsoft ever addressed this problem.

This might be a helpful real world tip to offer in the training video.

@Jeff-Hubbard,

Sorry, this post slipped by us. I will try to see what we can do. We've got some gaps in schedule coming up. This may be a topic that we might be able cover if there's a fix for it.

@Jeff-Hubbard,

Just did a little research, Microsoft doesn't have an automated way to do what you need to do. The reason, the Server Core will not update to the GUI is the original ServerCore source files are older than the newer Server Installation with Updates. So you must update the sources files for the original installation...but there is no automated way to do this.

You'll need to find the right version of your Server Core installation (Standard, Datacenter, etc) then look at files that have been updated and compare that Microsoft's update for them and download the latest ones to update that source. There are powershell commands to help you do that (i.e. add-windowspackage).

Thank you for replying. Since this feature doesn't work quite the way it is represented I thought it should be called out before people install a bunch of Core servers thinking they can switch back to GUI at any time with no hassle.

I didn't notice this in my labs because I keep it offline and didn't bother to update. I discovered it when I installed a Core DC at work for more PowerShell practice, updated and then decided to try adding the GUI back and found it doesn't work.