True, this is something that would need to be tested to ensure the updates from Server 2012 released February 2016 patch Tuesday and later months will all work on original Windows 8. As I said before, I emphasized that there is hope (in other words, just speculation). I would recommend testing (in virtual machine or a physical machine that isn't critical) on a clean original Windows 8 install, fully updated up to all January 2016, then patch with Server 2012 updates on the first patch Tuesday on February 9th, 2016 where original Windows 8 patches will be absent. If doing the testing on a main machine with Windows 8, I recommend backing up anything before you proceed. The patches I would watch out for and possibly avoid are the ones designed to fix issues only related to server components. It wouldn't be ideal to break the OS that fixes functionality issues that aren't existent in the workstation counterpart. Security related updates that fix discovered kernel exploits and .NET security updates should be helpful and shouldn't break. Internet Explorer 10 security updates should have no issues either. Backing up before each patch Tuesday is practical since it's unofficially supported and things have potential to break. I mean both Windows 8 and Server 2012 are the same codebase, run NT 6.2 kernel (Windows 8.1 and Server 2012 R2 are NT 6.3). It's just nice knowing that Windows Server 2012 will still be supported all the way until January 2023 and that the server counterparts were treated as separate paid products (as I said in my previous post) unlike the Windows 8 and 8.1 workstation counterparts where the support model itself is treated differently like service packs. Again, hope this is helpful. Even with a little convenience given up, you can possibly still patch original Windows 8 x64 (Windows Server OS's stopped being x86 since Windows Server 2008 R2).