Windows Server 2016 v1607 corrupted image

Question

I'm retooling my lab environment and trying to install a Windows Server 2016 Standard v1607 from an MSDN Subscription I had back from that time period, but the ISO image has some corrupted bits on it. 

Consequently some features of the OS are not working as they should. I have followed Tech guidance to trouble shoot, and found about a dozen DLLs that will not register correctly during installation. 

So I need to recreate an ISO image of the OS.

Used to be you could download a new ISO but that's no longer an option. So I ran SFC and DISM to repair those bad binaries, and on first attempt, only one new OS installation was fixed, a 2nd was not.  

I am repeating those steps as I write to see if a 2nd attempt will get it done. 

In the mean time I had a question about how to recreate a new ISO image. Can I assume correctly that by installing Windows Assessment and Deployment Kit, I can create a new ISO image that is the same version as the ISO I have a license for? 

And do so from good bits that WADK downloads? I ask because the 1607 version was a intermediate and transitional version of the OS that was eventually replaced by 1709 and 1803, and I want to be sure I'm getting as close as possible to the bits I need.,

Thanks in advance.

Answer 1

I suggest downloading the Windows server 2016 v1607 iso from the evaluation page (Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO ~6.5 GB). It supports Standard and Data Center editions and can be used with your retail key(s) or to repair your installations or corrupt iso if necessary.

Evaluate Windows Server 2016

Answer 2

Thanks for the link but unfortunately it did not work. After creating a new installation, I am unable to upgrade the trial key to a licensed key, the error message I get is, the trial version can't be upgraded. This is with the Server 2016 Standard Edition, I have not tried it with the Data Center version and the key I have for that, but believe the results would be the same.

The only changes made after a clean installation were to give the server a name only, while remaining in Workgroup mode, install File Server service, Storage Services, .NET Framework 4.6, WINS Server, PowerShell 5.1, DFS Mgt. Tools, File Server Resource Mgr, SMB 1.0/CIFS, Telnet Client, Windows Defender, and Windows Search Service.

With the Key Upgrade failing I tried running Windows Update to download the latest and greatest from MS, that failed too, which was the real problem I faced that cause me to ask for help to begin with.

That error code is (0x8024402f), the same error code I got on my corrupted ISO image, so I'm wondering now if that image is actually corrupt or something with Windows Update has changed. Having spent the day trying every suggestion in every post I could find, nothing has resolved this problem, so I'm leaning towards the conclusion that its a Window Update change that is the real cause for the 1607 update failure.

The Key I used was for Windows Standard, and it worked the last time I used it but that's been 2 maybe three years ago. So I have to believe there's something in the ISO that's preventing the key from working with the current version of Windows Update. There were some new steps with this new ISO that were not there before and perhaps, I made the wrong choices, but that's doubtful.

1607 seems to be DOA all around if a new image from MS can't get the job done. Any ideas on where to turn to next?

Answer 3

I forgot to mention in that previous reply, that in addition to those steps, I also went out to Microsoft Downloads and downloaded every manual Windows Update going back to March of 2018, and applying them one by one.

No problems doing that, all the Service Stack updates installed 1st time without problems, as well as the last 3 Cumulative Updates. I did not install any of the .NET Framework Updates since Framework 4.6.2 was already installed successfully.

Still got the same  (0x8024402f) error from Windows Update though which is why my conclusions was, its a change to Windows Update that is the underlying problem.

Your thoughts?