I'd been putting off the Windows 10 November Update since it showed up in Windows Update on Thursday, mostly because I wanted my weekend free for Fallout 4 and not for troubleshooting a Microsoft patch. But curiosity won out yesterday afternoon, so here's what actually happened when I ran it, in case anyone else is staring at that "Update available" notification and wondering if its worth the hassle.
Quick context for anyone who missed it: this is the first big update to Windows 10 since it launched in July, officially build 10586, unofficially "Threshold 2" if you've been reading the leaks. Its free, it comes through Windows Update like a regular patch, and Microsoft is treating it as basically mandatory going forward for consumer machines.
What you actually get. The Start menu got some layout tweaks (tiles resize a little more sanely now), Edge picked up the beginnings of extension support, though what shipped this week is really just a developer preview and not something you can install extensions into yet from the Store. Skype integration got baked into the lock screen and the Messaging app, which I have zero use for since I don't run Skype, and Windows Hello got some under-the-hood improvements for biometric login. None of it is dramatic. Its the kind of update where you read the changelog and think "okay, sure" rather than getting excited about anything specific.
The install itself. On my desktop (i5-4460, SSD, nothing exotic) the whole thing took 47 minutes end to end, including three restarts. That's longer than I expected for something billed as an incremental update rather than a full OS reinstall, and it ate close to 20GB of disk space during the process even though the net install size afterward is smaller. If you're running low on free space, check that before you start, because a failed install partway through the second restart is not a fun way to spend an evening. Mine didn't fail, for what its worth, it just felt slower than it needed to be.
The one actual problem I hit. After the final restart, my audio was just gone. Not muted, not wrong device selected, just nothing in the sound output list at all. Turns out this is a known issue where the update strips out third-party Realtek drivers and replaces them with a generic Microsoft one that doesn't always grab the right hardware. Fix was annoying but not hard: go to Device Manager, find the audio device with the yellow warning triangle, uninstall it, then go download the actual Realtek driver straight from your motherboard manufacturer's site rather than trusting Windows Update to sort it out. Took about ten minutes once I knew what was wrong, but if you don't know that's a known thing, you'll spend a while assuming you broke something.
I'll say this for it though: once everything settled, the machine does feel a little snappier on boot, and I havent noticed anything else broken after a full day of normal use. No Store apps vanished on me, unlike some of the horror stories floating around forums this week. Your mileage will genuinely vary depending on what drivers and startup software you've got installed, which is sort of the eternal problem with Windows updates in general and not really specific to this one.
If you're on a laptop with fussy vendor drivers (looking at you, anything from a certain Taiwanese manufacturer whose driver update tool I will not name but which has ruined more than one of my afternoons over the years), I'd wait a week or two and let other people find the landmines first. If you're on a fairly standard desktop build, its probably fine to just let it run whenever Windows Update decides to nag you about it. Back up first regardless. That advice never goes out of style, and I say it every single time one of these rolls around because I've learned it the hard way more than once.
Anyway. Fallout 4 is installed and waiting, so that's where the rest of my weekend is going.