Category Archives: Win10

Win10, Windows

Windows Keyboard not working Code 19 registry error

1 – Navigate to the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}
2 – Once you find the two folders, there is no need to expand them further (if you do, you’ll find folders labeled “0000”, “0001”, “Properties”, etc. — just ignore these).
3 – To fix the keyboard, click directly on the 4D36E96B-E325-11CE-BFC1-08002BE10318 folder (don’t expand it). Once you click the folder, you’ll see registry value files appear on the right hand side.
4 – The file you’re looking for is the last one in the group — the one named UpperFilters. Double-click on it, and a small box opens titled “Edit Multi-Screen”
5 – Once the Edit Multi-Screen box opens, you want to delete any information in the Value data: field (if there is any), and type kbdclass When finished, click the OK button.
6 – Reboot your system.

microsoft, MicrosoftSucksAss, Software, sysadmin, Win10, Windows

Disable the Cloud sign-in option on Office 2019

Note: Might be easier to install the admx admin templates to Group Policy Editor. See this post for more info

Office 2019 annoyingly wants you to sign in to either a domain or the cloud. It shares the same registry space as Office 2016, so the procedure is:

Preparation:

1. Note that this must be done on a per-user basis, for anyone who logins into the machine. So 2 users on the same machine = do it twice. Or if that user signs into another machine, do it again.
2. Go into one of the Office apps, go to Account, and select “Sign out” & then click Yes when prompted.

First, close all Office applications:

Word
Excel
PowerPoint
Outlook
etc.

Second, open the Registry Editor: (may need to Run As Admin)

Start > Run > regedit

Third, navigate down the tree:

HKEY_CURRENT_USER
SOFTWARE
Microsoft
Office
16.0
Common

Third, add the SignIn folder:

Right-click on the Common folder
Go to New > Key
Name it “SignIn” (without the quotes)

Fourth, add the registry key to disable the sign-in option:

Right-click on the SignIn folder
Go to New > DWORD (32-bit) VALUE
Name it “SignInOptions” (without the quotes)
Set the value to 3

Fifth, verify that it worked:

Open up Word
It should no longer have the “Sign in” button in the top bar
Under File > Account, all of the sign-in verbage should be gone

If you ever need to add it back in, just delete the SignInOptions reg key!

Source: Question – Tutorial: Disable the Cloud sign-in option on Office 2019 | AnandTech Forums: Technology, Hardware, Software, and Deals

microsoft, sysadmin, Win10, Windows

Could not authenticate to SMB share with correct creds [solved] : freenas

Could not authenticate to SMB share with correct creds [solved]

I solved this issue but wanted to share the solution.

I had set SMB permissions correctly according to this forum post and this video, but I was never able to access my SMB share.

I was able to see the server and the list of shares, but no matter what I could not actually open a share. No matter what user or group I used, each login from W10 would fail with ‘Access is Denied’ or ‘Incorrect user name or password’ or ‘Check with system admin to verify permissions’.

The first thing I wish I had known off the bat was that samba activity is logged in FreeNAS at /var/log/samba4/log.smbd. Tailing that log, it was obvious there were authentication issues. On each login attempt, I saw:

[2018/04/15 02:10:51.243374,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[$fnstorage]"
[2018/04/15 02:10:51.245286,  2] ../libcli/auth/ntlm_check.c:430(ntlm_password_check)
  ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user msUser
[2018/04/15 02:10:51.245752,  2] ../source3/auth/auth.c:332(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [msUser] -> [msUser] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2018/04/15 02:10:51.245837,  2] ../auth/auth_log.c:760(log_authentication_event_human_readable)
  Auth: [SMB2,(null)] user [MicrosoftAccount]\[msUser] at [Sun, 15 Apr 2018 02:10:51.245799 PDT] with [NTLMv1] status [NT_STATUS_WRONG_PASSWORD] workstation [win10-PC] remote host [remoteAddress] mapped to [MicrosoftAccount]\[msUser]. local host [hostAddress]
[2018/04/15 02:10:51.245934,  2] ../auth/gensec/spnego.c:605(gensec_spnego_server_negTokenTarg)
  SPNEGO login failed: NT_STATUS_WRONG_PASSWORD

Now at first glance, what jumps out is NT_STATUS_WRONG_PASSWORD, you might think you’re just typing your password wrong. But that’s not what’s really going on– the real culprit is

ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user msUser

You may remember that NTLMv2 is the standard for SMB security, and NTLMv1 authentication is disabled by default in FreeNAS SMB shares.

I figured my PC was using NTLMv1 for some reason. A little research led me to this GPO in Group Policy:

 Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\LAN Manager authentication level\

Set this to Send NTLMv2 Only instead of whatever else it is. Mine was set to Use NTLMv2 if negotiated. See Microsoft’s docs for the caveats here.

I’m not sure if the value my PC was using is default, and I’m not sure if FreeNAS should actually negotiate NTLMv2, but this resolved my issue with no impact to other SMB shares on my network.