This month’s Windows 8.1 patch apparently disables Microsoft Account login

Topic

New Reply

There are lots of hints around the web that this month’s KB 4038792, the 2017-09 Monthly Rollup for Windows 8.1 and Server 2012 R2, is leaving Win 8.1
[See the full post at: This month’s Windows 8.1 patch apparently disables Microsoft Account login]

1 user thanked author for this post.

MrBrian

Reply | Quote

Replies

LOL, as one who relies on Win 8.1 and has been using a local account forever, a very old adage pops to mind:

That’s not a bug, that’s a feature!

In all seriousness, it’s egregiously bad when Microsoft releases patches to older OSs that just break basic things, given that it pushes people perhaps not so gently toward their “shiny new” Windows 10.

Presumably at least SOMEONE inside Microsoft uses a Microsoft account and tested the patches for Windows 8.1? Anyone? Are these things really coming out without ANY testing whatsoever? Or does no one inside Microsoft use a Microsoft account?

For what it’s worth, with a Win 8.1 system already set up using a local account the patch seems to work fine. I’m not having problems with it, with more than a week’s usage on my main workstation.

-Noel

3 users thanked author for this post.

Elly, Karlston, HiFlyer

Reply | Quote

that’s weird. I have KB4038792 installed on my father’s Toshiba Win8.1 laptop which IS using his MS account and not just a local account and I’m not having any login problems with the patch. WiFi internet connection enabled at startup as well.

1 user thanked author for this post.

HiFlyer

Reply | Quote

That IS weird. Are you sure it’s KB4038792, and that you’re using a Microsoft account?

Martin also reports that

The connection during the update process was terminated for some users who tried to update the Windows 8.1 machine to the latest roll up update.

1 user thanked author for this post.

HiFlyer

Reply | Quote

If I recall correctly, the initial install of Win8.1 did a good job of hiding the fact that you COULD have a local account. It was:

Login with your Microsoft Account.
Don’t have a Microsoft Account? Create one.
Next screen: entry boxes for creating MS ID and Password – and at the bottom in tiny letters a link that said “Keep using your current Account” that let you create the Local Account. (Didn’t mention it was a Local Account or that you were creating it)

About like clicking the Red X meant “agree” !!!

6 users thanked author for this post.

Elly, Karlston, David F, HiFlyer, Microfix, woody

Reply | Quote

Any reports on KB4038793 ‘security only’ patch for those who actually use an MS account?

Windows - commercial by definition and now function...

1 user thanked author for this post.

HiFlyer

Reply | Quote

I haven’t heard – and I don’t know if manually uninstalling the patch (assuming you have a Local account with admin privileges) brings back the logon ability.

I was going to test a bunch of variations when I discovered this morning that my main machine’s Hyper-V lost its ability to connect to a virtual Ethernet switch. No idea how it happened (probably moving from 1607 to 1703), and there was no easy fix in sight. So I decided to run with the observations from, oh, about a zillion people.

2 users thanked author for this post.

HiFlyer, Microfix

Reply | Quote

I got it and have had no problems with Microsoft accounts.  KB4038792 failed on me for some reason.  I have had problems with Firefox, but a re-install seems to have fixed that.

 

Reply | Quote

I would have thought that Microsoft would want to disable the local accounts rather than the Microsoft accounts. In other words, I don’t believe that this was intentional on Microsoft’s part.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

3 users thanked author for this post.

Elly, HiFlyer, Microfix

Reply | Quote

All the more reason why it’s weird MS hasn’t fixed the problem in the past two weeks.

2 users thanked author for this post.

HiFlyer, Microfix

Reply | Quote

woody wrote:

All the more reason why it’s weird MS hasn’t fixed the problem in the past two weeks.

Who knows what evil lurks in the hearts of men….er, Redmond?

Reply | Quote

” In other words, I don’t believe that this was intentional on Microsoft’s part.”

So what?  Malicious act or negligent error.  The result is the same — users pay the price.

Reply | Quote

From Cannot login with Microsoft account: “We’re aware of this matter that affected a small subset of our users in certain areas when logging into their Microsoft accounts. Our engineering team is working hard to find and fix the reason for this known bug. We’ll provide you with updates as soon as possible.”

Reply | Quote

I can confirm that I’m able to login with an MS account on a Windows 8.1 Enterprise (64-bit) system that does have KB4038792 installed.  I just did a reboot of Windows and my “cloud” login still works.

 

2 users thanked author for this post.

HiFlyer, MrBrian

Reply | Quote

MrBrian wrote:

From Cannot login with Microsoft account: “We’re aware of this matter that affected a small subset of our users in certain areas when logging into their Microsoft accounts. Our engineering team is working hard to find and fix the reason for this known bug. We’ll provide you with updates as soon as possible.”

Apparently I’m affected – just tried to login to my MS account (have been always using Local account) and connection cannot be established.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

3 users thanked author for this post.

HiFlyer, Noel Carboni, MrBrian

Reply | Quote

Not a lot of uproar here. Could it be that many/most Windows 8.1 users have seen the light and were already using local accounts?

On the one hand, if you were a Metro/Modern App afficionado using Win 8.1, you may have wanted Windows 10 right away and took the upgrade when Win 10 was released.

On the other hand, if you (like me) de-configured the App junkware and made Win 8.1 back into a pretty decent desktop system, then you really had no reason to want or use a Microsoft account and have been using a loca account all along. Thus you wouldn’t be affected by this new problem at all. From what I can see it’s the only patch regression documented this month.

It’s been a week and a half now, and I’ve seen no problems whatsoever with the September “Group A style” Win 8.1 updates in hard system use. Reliability has been solid, and my performance is as good as ever. Yesterday evening found me building up to 4 projects simultaneously with Visual Studio in preparation for three releases of my software. It all came off without a glitch.

It seems funny but I consider Win 8.1 (suitably reconfigured) the best OS Microsoft has ever released.

-Noel

3 users thanked author for this post.

HiFlyer, Elly, NetDef

Reply | Quote

I’ve several users that still use 8.1 – no problems so far.

Granted the scenario is not exactly the same:  these are AD (domain controller) accounts that are linked to a MS account so they can use the store and OneDrive.

~ Group "Weekend" ~

1 user thanked author for this post.

Noel Carboni

Reply | Quote

Reply | Quote

As an 8.1 user myself I never saw any point or benefit to making a Microsoft account, after seeing this post, I’m going to make sure never to make one.

Reply | Quote

Oh my, I have not yet installed this patch on my W8.1 X64 system because after the last run of bad patches MS has released over recent months, I have grown exceedingly cautious and really drag my feet on monthly cumulative rollups. One observation I would make is that given the nature of problems that keep cropping up each month, it has become really difficult to believe that MS has any quality assurance testing that is worth the term. Are we to accept that any reasonable QA pre-release testing program would not detect the inability to login to your MS account? If so, the world has indeed become a very strange place!

1 user thanked author for this post.

HiFlyer

Reply | Quote

I have a Windows 8.1 Enterprise (64-bit) system that has KB4038792 installed and only has a single MS account enabled and I’m still able to login same as always.

Reply | Quote

Well I am facing a problem because of this, hope they fix this.

Reply | Quote

My store bought Asus laptop came with Win 8 preinstalled when I bought it in Nov.2013.  When 8.1 was offered, I accepted it.  Since then for the life of me there has never been a single indication that an “account” was required.

Being in group B I installed Sep.4038793 (2017-09 Security Only Quality Update for Windows 8.1 for x64-based Systems).

On my buddies Win 7 x64 on the older model Asus laptop (also group B & no knowledge of an account) we installed Sep.4038779 (2017-09 Security Only Quality Update for Windows 7 for x64-based Systems).

So far so good.  Unless I missed something, seems that a bullet was dodged to a degree.  Gotta hunch that not having an account might not be too large a concern.

Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

1 user thanked author for this post.

HiFlyer

Reply | Quote

Purg2 wrote:

  “On my buddies Win 7 x64 on the older model Asus laptop (also group B & no knowledge of an account) we installed Sep.4038779 (2017-09 Security Only Quality Update for Windows 8.1 for x64-based Systems).”

I think you meant for “Windows 7”

 

1 user thanked author for this post.

Purg2

Reply | Quote

The edit button is gone on that post or I’d fix it.  Thanks for pointing that out HiFlyer.

Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

1 user thanked author for this post.

HiFlyer

Reply | Quote

Gotcha covered. My edit button is still there.

2 users thanked author for this post.

Purg2, HiFlyer

Reply | Quote

PK, always on the ball.  Thanks for the edit favor.

Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

Reply | Quote

Duh, in an effort to be thorough I inadvertantly included W7 info which does not apply to this W8.1 issue, face/palm.  Silly Purg, stop getting distracted by shiny objects, heh heh.  Too many Woody tabs got me gooped up.  Ambles off abashedly.

Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

1 user thanked author for this post.

HiFlyer

Reply | Quote