New
#250
bit of a "ruff" build this one
Lol, true. I'm actually not complaining, although with 17046 I was complaining a lot near the end. But when a build starts automatically suspending your installation processes when you are reinstalling a bunch of software, you (I) get irritable, even vexed.
I can deal with a warning flag, and I can deal with no sound in Firefox as I have plenty of other browsers to use for audio. And I've not had a single reference to my activation being in jeopardy, so I am good.
But now I have sound in Fx on the newest Nightly, and I've had my machine on for 3+ hours and still no warning label on my defender icon, so everything seems hunky dory again.
No, I meant the recovery partition - I don't have UEFI on my desktop.
It might have changed, but last I checked, if you created a partition on a drive and then told Windows to install into that partition and there was no free space left on the HD, it did not create a recovery partition, even in clean installs. So, that is why I just clean and let Windows used the entire unallocated drive space to create the system partition (and whatever else it wants to.
Verified.
Odd. I've got a 970 and a 560 Ti 448 Core, and I had the drivers from 5 Dec (388.59) installed, and 17063 installed with them and did not revert them to a previous version like it has in almost every previous IP update....
Of course, nVidia just released 388.71 2 days ago, so now I am on that build instead.
About that (not)funny warning about License to expire soon message.
Is there any edition that comes with time limited license ?
Does that mean that rumors about plans for switching to prescription model are true ? (Windows 365) ? What about leap year ?
keeping an eye on event viewer.
changing Internet security fixed some errors.
license manager error still there.
windows update error.
not a giant amount, but a few popping up here and there.
31 entries in System
50 in application
95% are information entries.
When people get that sort of message it generally means they had a kms key usually with some illegal software that fooled OS into keeping it activated without doing an "ET phone home" activity periodically ie contacting the KMS server to revalidate key. Upgrades have a habit of breaking the illicit software and you then get the error mesage.
Certainly not in my case. This one comes from retail W7 from one of it's first days, updated to SP1, than used for years before upgrading to W8 > 8.1 and all W10 insider versions since day one of W10. The only difference from store bought W7 is that it was bought as cheap (something like 15 -20 or 40 bucks as upgrade from Vista). Entering original license doesn't produce any different results.
MS has acknowledged the proeblem
"ADDED 12/21: We are investigating reports that Windows shows that it “needs activation” and trying to activate fails after upgrading to Build 17063."
And I'm confident it will be fixed but caused me some anxiety by than. For now it's just a temporary nuisance.
mine came from a laptop upgrade to win 10