??? Obviously there isn't an updated version. Anyway I wasn't looking for help, just reporting a simple case of consistent crashes on servers. For the record it's now three months that my 2016 runs as 2012 R2 guest, with the HDDs connected to it in passtrough
Update: The upgrade at home was successful. I brought the VHD back to work and loaded it on the 2008R2 server where it came from. BSOD on boot. Moved VHD to the 2012R2 host, built VM around it, and it boots up and works. Conclusion: Server 2016 TP5 will not work on a 2008R2 Hyper-V host.
Did you try to do a fresh install of "Windows Server 2016 TP5" on a 2008R2 Hyper-V host ? What build/version of Hyper-V was the original VHD from/on ?
It's not supposed to work, and it doesn't work 2012R2 isn't supposed to work as well, but practically it works flawlessly (if you have KB2744129 installed on your server 2008r2)
Windows 10 Anniversary Update seems to be finished, weren't Server 2016 supposed to based on the same build? Yet we still have to wait until late September for the release?
I am hoping that partners will be handed this build sometime before September and that we see a leak prior to then. Otherwise, we'll be waiting quite a while before we get our hands on this.
I wasn't referring to WZor specifically on this. Maybe wishful thinking on my part - but hopefully if the partners/OEMs get this build before the end of September that means that we will, too.
I can not get it to install on HP with Intel P4 Ht with 4 gigs of ram 160gig harddrive. Hangs as it installs, shows windows logo
The partners/OEMs are getting a serialize (digitally signed) version of Server 2016, not too sure how it work completely, but the master copy have a code on it, but when it's install the code is not on the machine you installed it on. It is only on the master iso, so if you copy that dvd it will have this code, then MS can track which partners/OEMs dvd got leak. Not sure if MS will make a corporate iso with the code in it. I always think the RTM was the master image, but it's not.
Microsoft has on prevoius occasions included a uuidref code in ISOs that it has released. Which then leads to different sha1 for each ISO. If you know what to look for, you could blank it out with a hexeditor. Or remaster ISO without the uuidref.
Just freshly installed TP5 + updates, it is showing RS1 build 14300. Would it be possible to extract dedup package to use with W10 AU 14393?
build 10586 had the "Technical Preview" label in WIM files and both 10240/10586 have the Microsoft-Windows-Prerelease-Client-Package some cosmetic slips here or there doesn't mean the build is not RTM
label doesn't effect the OS in anyways, this does this package relate to insiders there no timebomb so RTM or pre-RTM
Still, if msft isn't considering (or signed) 14393 as server RTM, they could choose any other build to continue TP series
I do not know if this is accurate - look back through his posts, he had a leak for Server 2016 14291 ISO before TP5 (14300) was officially released.