Hopefully 17133.73 stays as 'RTM'. I clean installed this build with love and care. It's clean, fast and tailored to my needs after a couple of hours. I'm lazy to do it again for the next build that gets deemed as 'RTM'. T_T Edit: Why can't they release the next possible 'RTM' as an update (eg 17133.xxx) and needs to be done as a whole build instead?
Build 17133.1 (including 17133.73 or not) might have first stage install process issues which prevent user from installing updates.
Wasn't there a trick long ago where you modify a file in the INF folder making these components removable? Its been a while and I don't remember the procedure precisely, maybe someone here knows what I am talking about.
lol. Since when I've said anything about "dangerous", etc? No need for all that drama. Please read my post again without the glasses of a sys-admin, because it clearly wasn't intended to do so. "problem for gamers" makes it clear if you missed that bit. It's just a big nuisance if you're a gamer playing recent stuff and require the latest driver to properly play a game, or have a brand new GPU that is unsupported in the last working set for your deprecated OS (WDDM requirements being an example). In the last example, it's almost a 12 month wait to be able to use current 2.3 drivers under LTSB, and this is completely out of pace with the gaming market.
Do you mmean uninstalling network adapter and its driver from Device Manager? If so I could remove my Ethernet, wireless adapter,Bluetooth Device (Personal Area Network) and Bluetooth Device (RFCOMM Protocol TDI) and reinstall them as before with no different. If you probably mean removing the Ethernet/Wi-Fi/Bluetooth Network Connection entries from the network connection folder, yes you cannot, but it's not something new. I think it's was not possible to remove those for a while.
Everything I need is working just fine, but my gaming laptop is hotter on 17133.73. I just don't feel comfortable with that. It was quite cool on RS3.
Had random memory leaks with 17133.1 but couldn't identify the program causing it, so I reverted to 1709 for now.