SoylentNews is people
SoylentNews
A bug in Microsoft's activation server has led to pandemonium among people trying to activate or re-activate their Windows 10 Pro licenses. No need to panic. Microsoft will fix it "within one to two business days." (Try telling your boss that.)
If you see a bogus report about an invalid Win10 Pro license, relax. It's just Microsoft's servers screwing up, again, and everything should be copacetic in a couple of days.
On Twitter, Windows leaker emeritus Faikee posted this screenshot:
[...] There's also a lengthy diatribe on Reddit.
[...] The only breath of hope that I've found comes from the Microsoft Answers Forum, where Daniel Randy quotes a Live Agent response as saying:
Thank you for sharing, Daniel. Microsoft has just released an Emerging issue announcement about current activation issue related to Pro edition recently. This happens in Japan, Korea, American and many other countries. I am very sorry to inform you that there is a temporary issue with Microsoft's activation server at the moment and some customers might experience this issue where Windows is displayed as not activated.
Our engineers are working tirelessly to resolve this issue and it is expected to be corrected within one to two business days, Daniel.
But Ask Woody says it's fixed now:
I followed the updated troubleshooting steps posted by João Carrasqueira on Neowin and, bada-boom bada-bang, it’s all activated now. The Steps:
- Click Start > Settings > Update & Security
- On the left choose Activation
- Under the top section, click Troubleshoot
(Score: 5, Insightful) by edIII on Saturday November 10 2018, @12:20AM (16 children)
The strongest cheerleader for Linux and BSD will always be Microsoft :)
Yet another reason I'm glad I finally quit Windows.
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 3, Touché) by takyon on Saturday November 10 2018, @12:23AM (14 children)
One day we will be able to install Microsoft Linux.
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 1, Funny) by Anonymous Coward on Saturday November 10 2018, @12:28AM
No. One day you'll be able to buy install disks for Microsoft Linux. Will you be able to install it? That's the usual Microsoft Crapshoot 1.0 (TM)
(Score: 2) by NotSanguine on Saturday November 10 2018, @12:32AM (12 children)
Actually, you [zdnet.com] already [microsoft.com] can [microsoft.com].
Good Times! [youtube.com] :)
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by takyon on Saturday November 10 2018, @12:38AM (11 children)
Yeah, but wut about a Microsoft Windows® Linux® for The Desktop?
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 3, Interesting) by edIII on Saturday November 10 2018, @12:44AM (7 children)
I would actually like to see Microsoft do that. Heck, I might even buy a copy.
At one point, they were actually competent enough to make decent administrative controls and user interfaces to control your system. The default libraries were pretty damn good, and using Windows objects was fairly painless. If they dropped their own OS entirely, and took a Linux flavor and developed everything on top of Linux, they have a pretty damn decent chance of making an impressive window manager.
You piqued my curiosity on this one. I wonder what that OS would look like? Of course this assumes they could drop telemetry and Cortana sucking all data up like the damned InfoSphere. Which is like saying a crack whore can reform and stop sucking dick for loose change. Which is to mean, possible, but highly unlikely.
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 4, Interesting) by NotSanguine on Saturday November 10 2018, @01:21AM (5 children)
Interesting. I've often wondered myself what might have been if Novell had ported Netware to Unix back in the 90s, rather than sticking with their crap server UI. They had the edge in file/print services as well as huge market share. And the NDS (x.500) directory was years ahead of Active Directory.
I kept waiting for them to announce such a thing after they bought Unix [wikipedia.org], but it never happened. and when developers can develop on the platform for which they're writing (cf. nlm [v3.co.uk] development [drdobbs.com] was always painful), they will do so much more frequently. What's more, the hassles of managing implementation of NLMs made Netware an inferior application server. More's the pity.
Then again, if Ray Noorda and Novell had gotten it together back in the mid 90s, we might be bitching about them instead. :)
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by black6host on Saturday November 10 2018, @02:05AM (2 children)
The problem with Novell, and I've worked with it a bit back in the day, was that writing applications for the server was a pain in the ass. Windows server came along and while it sucked in comparison to Novell every Tom Dick and Harry could write a server app for it. Eventually Windows Server got better though its niche is business. Of course, that's where all the money is :) I really hoped for Novell, OS/2 and Delphi. Please, don't anyone ever hire me again! :)
(Score: 2) by RS3 on Saturday November 10 2018, @03:02AM (1 child)
Did you do .nlm development?
(Score: 2) by black6host on Saturday November 10 2018, @03:54PM
No I had my hands full running a team that was writing our in-house applications which were all designed around our business (basically an auto club like AAA.) We used the Advantage Database Engine which ran on the server. We were consumers of server apps but not developers. This was back in the 90's sometime. Can't remember exactly when, it was that long ago :)
(Score: 2) by RS3 on Saturday November 10 2018, @03:00AM (1 child)
> Interesting. I've often wondered myself what might have been if Novell had ported Netware to Unix back in the 90s, rather than sticking with their crap server UI. They had the edge in file/print services as well as huge market share. And the NDS (x.500) directory was years ahead of Active Directory.
Hmmm... I miss that server screen saver! Back in those days we had much less RAM. In roughly 1994 I remember 16 MB RAM cost $2,000. The point of Netware was that it was a bare-metal OS, running the x86 at maximum efficiency. Having done a bit of assembly and studying clock cycles per instruction depending on which mode the CPU ran in, you learn that you gain a huge number of clock cycles per instruction- mostly ones with memory fetch- in protected segmented mode. I once wrote a cogent argument (for one of our salesmen) for why our Novell-based systems were better than Unix / Windows (even though I was a Linux fan)- that the server was a maximally efficient server- no GUI stuff. I even wrote that people can't play games on the server.
You really didn't do much server admin on the server- mostly done on a workstation. The older tools were full-screen text menu-driven, and newer ones were Windows GUI, but the server is just a server. Even now I run my Linux servers in text mode only. Trivial to run GUI apps on a workstation though the network if I need them, although I pretty much never do.
I did .nlm development. Nothing went to customers, but certainly could have. Still have the books, Watcom compiler, etc. I don't remember any pain, just a bit of learning Watcom and the usual API stuff. Bringing back memories...
My only criticism of Netware was that it was cooperative multitasking. But again, remember the CPU speeds and available RAM in those days (early to mid 1990s).
You probably know Linux supports IPX/SPX well.
Yes, I agree Novell should have built better GUI admin tools sooner.
I think they would have helped themselves by fully supporting NFS on TCP/IP, and SMB.
Yes, NDS was way ahead of MS.
I blame MS general heavy-handedness, and razzle-dazzling non-technical business people who made the decision about which OS to run. Also, I've heard horror stories about Novell's business practices, although I never experienced any. I just remember how efficient Netware was. I thought "elevator seek" was brilliant, for example. I'm still not sure what a "bindery" is nor why I need one.
(Score: 0) by Anonymous Coward on Saturday November 17 2018, @12:11PM
It really incensed me since their reasoning was so retarded given the other crap they have been bloating the kernel up with. IPX is not a security issue if it is not used, and deprecating it or defaulting it off would solve any security issues if not maintainability ones.
Seems like the Social Jackoff Warriors are winning at making Linux as handicapable as they are.
(Score: 2) by aristarchus on Saturday November 10 2018, @08:04AM
Shirley, you jest? Do you mean KDE? Or XFCE? I really do not think that M$ could manage a decent window manager, without having to include a whole damn fucked-up operating system and DRM and Registration, and phoning-home, and Key-Logger, and, well, without Micro$oft. Sucks to be them.
I don't think I have ever had a problem with a Linux Distro Authentication Server going down. Ever.
(Score: 2) by NotSanguine on Saturday November 10 2018, @01:23AM
An excellent point. That sounds like a job for [cue fanfare] Takyon! :)
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by requerdanos on Saturday November 10 2018, @01:41AM (1 child)
What I wonder is how the GNU folks feel about "Windows Subsystem For Linux" allowing you to download various distributions of what is essentially the GNU operating system--with the Linux part removed ("Today, the part of Linux will be played by a shim between GNU userland and the Windows kernel")--and calling it "Linux".
(Score: 3, Interesting) by NotSanguine on Saturday November 10 2018, @03:56AM
That's called Cygwin [cygwin.com] (wikipedia link [wikipedia.org]) and pre-dates WSL [microsoft.com] (wikipedia link [wikipedia.org]) by at least a decade.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 1, Insightful) by Anonymous Coward on Saturday November 10 2018, @05:06AM
This is the BIG reason we want Microsoft to NOT meddle in Linuxland and royally bollocks things up. Silo Windows, Apple and Linux in separate bins that don't mix, don't cross-contaminate and don't cross-spyware. Thank you.
Just yesterday I went to help (yet another) elderly victim of Windows 10. Flavour of the day - "wifi problems." What a moronic interface, designed for retards and the half-blind. How can anyone use this thing and stay sane? Windows reduces a nice-ish desktop to a child's toy, and a broken one at that.