I normally use a local account on Windows, although the Microsoft apps use a Microsoft account.
When I briefly switched to Microsoft account on Windows a few months ago it seemed to push me to having to use a PIN to sign in instead of a password.
If you go to Settings>Accounts>Email & accounts, is your Microsoft account listed there, with your user name (usually your e-mail address)?
Also, if you go to Settings>Accounts>Sign-in options, try selecting "password".
Yes, it is
Good catch, strangely enough the password-option is missing :-(
This seems rather strange to me as I have not changed the login settings via gpedit.msc
I did a few quick searches and fail to find any active group policies that could affect those login options.
However, I found a supposed fix telling users to delete the content of "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" to fix issues with the pin-login - however, after taking ownership of this folder, I realized that it is already empty.
Similarly, enabling "Turn On Convenience PIN Sign-in" via the group policies does not change the error message for the pin-login option.
Thank you for your assistance
I have created a thread in the support forum, to not hijack this thread any more than I already did.
https://www.tenforums.com/general-su...ml#post2109035
Of course I am mad, and I have the proof: With an academic background as a medieval historian, I have started TWO fire departments, serving as the first volunteer fire chief and then the first career fire chief of the first department, first volunteer fire chef of the second. Even worse, I am proud of that....
As for the percentage going backwards, I thought it was just an example of New Mexican mathematics. This is not the first time I have seen this, but given the problems I had been having in updating from 1909 to 20H2, it did concern me.
Just finished an in-place repair install on this computer to get to 685. Was at 662. Previously the KB4592438 update would show to be installing and when I did the required reboot the system would go to the blue windows screen with revolving wheel and then go to a black screen with the revolving circle and stay there. Forced restart would reboot into Windows with the message that update could not be installed. SFC showed no errors and DISM also did not show any problems. Had successfully upgraded 4 other computers including 1 laptop with the KB4592438 update but this computer would not update. Tried to reinstall several times but same result. Windows troubleshooter showed no problems. Should have went the repair route several days ago, would have been much less frustrating. The computer is now updated to 19042.685.
Not sure what to think of this info if true.
Running ChkDsk on Windows 10 20H2 may damage the file system and cause Blue Screens - gHacks Tech News
There saying Check disk corrupts the windows system files.
Eek!
Well I'm certainly not risking running chkdsk after reading that.
The danger is that it can run automatically on boot if it detects anything amiss with the file system of course!
If the report is true, that's a pretty serious problem.
Thanks for posting this. I would assume it's true for now:
Windows 10 20H2: ChkDsk damages file system on SSDs with Update KB4592438 installed | Born's Tech and Windows World
Vorsicht Datensalat: chkdsk c: /f auf Windows 10 20H2 beschadigt Dateisystem - Planet 3DNow!
They say that running Chkdsk C: /f on a 20H2 system with an SSD after installing KB4592438 corrupted the file system. Your link says: "Günter Born provides details on the issue on his blog." where he says that "...the logical Windows drive on the disk was detected only as a RAW partition. The /f option of chkdsk probably destroyed the NTFS file system."
Well, there's only one way to test this, so I ran Chkdsk /f on one of my SSD machines. Nothing bad happened....
It may (or may not) be relevant that since installing KB4592438 I had run Disk Clean up and cleaned up Windows updates.
Thanks for testing, I was going to say we could stop the auto check disk setting on reboot till this gets looked at.They say that running Chkdsk C: /f on a 20H2 system with an SSD after installing KB4592438 corrupted the file system. Your link says: "Günter Born provides details on the issue on his blog." where he says that "...the logical Windows drive on the disk was detected only as a RAW partition. The /f option of chkdsk probably destroyed the NTFS file system."
Well, there's only one way to test this, so I ran Chkdsk /f on one of my SSD machines. Nothing bad happened....
It may (or may not) be relevant that since installing KB4592438 I had run Disk Clean up and cleaned up Windows updates.
Disable or Stop Auto CHKDSK During Windows Startup • Raymond.CC
Cancel a Scheduled Chkdsk at Boot in Windows 10
well MS did release a new set of 20H2 ISOs with build 19042.685 (KB4592438 CU integrated) to MSDN/MVS subscribers a few days ago
Windows 10: ISO refresh for December 2020 (1809 – 20H2) - Born's Tech and Windows World
I did an in-place repair upgrade on a test PC using the newly released December 2020 refreshed 20H2 ISO w/ .685 already included
Quote
