Ha haI hope that your Blu-ray drive issue is resolved soon to your satisfaction.
If this was on a clean install that would be quicker to get to the how and why but since one been using and constantly updating Windows the problems become more and more murkier as updates continue to hide where the problem was unless it was discovered as Windows fault or user fault. Only real test would be two computers same hardware/software running the same process to verify problems and diagnosis where and how the problem occur would most likely show up but if it's so few that others don't experience the same problem then it becomes a user issue software/hardware glitch that can't be reproduced by others to get to the bottom of the problem.
This is why I never blame just the software unless everything else was update before just blaming Windows-which is a convenient O/S to blame for all sorts of plagued problems but it gets that notoriety regardless.
And why must one listen to this? 1709 is the latest and so far the problems I had are the same "hibernating" doesn't work properly and this has happen since 1607 release - so to say no one should go to 1709 has no real merits to backup. As for IT you should know that a update O/S is better then a open Border O/S - this should be known to all IT regardless of the O/S version. The IT does the Company Software update not the users of the computer they don't have access to do that. Here's another why are you playing around on the Company work computer - guess one doesn't have enough work hours to do work? For infections that is something no IT can stop as malware was written specifically to get past that and for users to "click happy" on any links that shows up on their email but then again you have to ask why are you using your work email for personal uses at work? I got 17090 installed and running all the latest RedFox and Elybyte(bad spelling) and they work just fine I know past 1607 with CloneBD backups work just fine and had no problems.
This kinda response is why in my years of learning that when one makes work status claims I highly doubt the work status is really true. Uses of "F" language is a big indication one doesn't work in the industry they claim to be in. IT is there to find and fix or diagnosis solutions and find preventative measures. All and any O/S from Windows always had issues it's how you mitigate it that determines how useful it is to the users. Now for your one that is different but to say 1709 isn't something anyone should use because it wasn't bug free is hard to expect and I think most Windows O/S users know this already. I would install the latest O/S minus Windows 8.1 debacle because it helps the user learn better and update software helps with their security more. This is why I never say I worked in this Industry for *blank* years so I know better that is never true statement to make. But I tell others it's better to have a O/S you can learn more about and at least expect most bugs in previous to be fix and there will be knew one that comes along with a new O/S release that just how releases go. At least with 1709 attempts where made to resolve issues from previous early release of Windows 10 and that to me is better then nothing. I went from 1607 to 1709 because this like Windows 7 SP1 release and having used the Windows 10 already I expect some issues. No O/S is nor will be perfect but having a Fall CU update was something that help more then it hinders.
