Out of band OPTIONAL Microsoft Windows versions 1903 & 1909 update/fix released February 28, 2020

 Some users were adversely affected by some patches/updates applied on February's Patch Tuesday update.
 A optional update   KB4535996 was released. As it is optional you may need to search Microsoft's sites or use Windows Update to find this fix.
 Fix, did i say fix?

Here is what is fixed in the new update:

• Fixed a speech platform issue that prevented it from opening in "high noise environments".
• Fixed a Windows Mixed Reality home environment issue that reduced the image quality.
• Fixed a PeerDist-encoded content issue in Internet Explorer and Microsoft Edge.
• Fixed an ActiveX issue that might prevent it from loading.
• Fixed an issue in Microsoft browsers that might cause the browsers to bypass proxy servers.
• Fixed an issue that could prevent Centennial apps from opening.
• Fixed an issue that prevented the installation or upgrading of UWP apps in some situations.
• Fixed a Microsoft Narrator issue that caused it to stop working if a user session exceeded 30 minutes.
• Fixed an update issue that caused an unwanted keyboard layout to be set as the default after upgrades or migrations even if it was already removed.
• Fixed an unmentioned issue when editing MOV file properties.
• Fixed an issue that caused usbvideo.sys to stop working after a device resumes from Sleep or Suspend after using the Camera app or Windows Hello.
• Fixed a Group Policy issue that caused the policy "Allow uninstallation of language features when a language is uninstalled" from taking effect.
• Fixed a Windows Search box issue that prevented it from "rendering fully in the space allotted for it2.
• Fixed an Input Method Editor issue that prevented the use of the user dictionary when "leveraging folder redirection with user profiles".
• Fixed a Windows Search issue that prevented it from showing results.
• Fixed an issue that caused the Windows installation to stop responding on a VMWare guest machine wit a USB 3.0 hub.
• Fixed an unnamed Windows Autopilot self-deploying mode and white glove deployment issue.
• Fixed a PowerShell workflow issue that might make these fail with compilation errors for long sessions.
• Fixed a product key activation issue in a user's Managed Service Account in the Windows activation troubleshooter.
• Fixed an issue that caused applications deployed using the Microsoft Installer from being installed using the mobile device management platform
• Fixed an "unknown username or bad password" error when attempting to sign in in an "environment that has a Windows Server 2003 domain controller (DC) and a Windows Server 2016 or later DC".
• Fixed an issue with sign-in scripts that caused them to fail to run.
• Fixed a data collection issue with isTouchCapable and GetSystemSKU.
• Fixed an issue that caused AAD joined systems to rejoin the AAD domain.
• Fixed an issue with the WinHTTP AutoProxy service and the maximum Time to Live on Proxy auto-configuration files.
• Fixed a printer selection issue in the SQL reporting service that caused the wrong printer name to be selected.
• Fixed a printer user interface issue that prevented it from being displayed correctly.
• Fixed a Network Profile Service issue that might cause the computer to stop responding.
• Fixed an issue that could cause some applications to fail to print to network printers.
• Fixed an issue that caused some printers to be a hidden device in Device Manager.
• Fixed an issue that caused Host Networking Service PortMapping policies to leak.
• Fixed a stop error that occurred when mounting Resilient File System volumes without a physical device.
• Fixed an Open Database Connectivity issue that caused an infinity loop.
• Fixed an issue that caused the Local Security Authority Subsystem Service to stop working and to trigger a restart of the system.
• Fixed an issue that intermittently generated Online Certificate Status Protocol (OSCP) Responder audit event 5125 to indicate that a request was submitted to the OCSP Responder Service.
• Fixed an issue that caused queries against large keys on Ntds.dit to fail with the error, “MAPI_E_NOT_ENOUGH_RESOURCES”.
• Fixed a log corruption issue when a storage volume is full.
• Fixed an unnamed error that caused _NFS4SRV_FILE_CACHE_ENTRY and DirectoryCacheLock to stop responding.
• Fixed a Server Message Block Multichannel issue that prevented it from working within a cluster network that has IPv6 Local-Link addresses.
• Fixed an issue that could cause Storage Migration Service inventory operations on a Windows Server 2003 source computer to fail in clustered environments.
• Fixed a timing issue that could lead to the stop error 0x27 in mrxsmb20!Smb2InvalidateFileInfoCacheEntry.
• Fixed an issue in the Storage Migration Service that caused the Cutover stage to stop working during migration if an administrator assigned a static IP address to the source adapter.
• Fixed an issue in which canceling a deduplication (dedup) job to rebuild hotspots prevented other deduplication PowerShell commands from responding.
• Fixed a Remote Desktop session disconnect issue.
• Fixed an issue that made Windows Defender Application Control's Code integrity-based events unreadable.
• Fixed a certification issue that caused Internet Explorer mode on Microsoft Edge to fail.
Improvements:
• Battery performance during Modern Standby mode improved
• Improved Event Forwarding scalability to ensure thread safety and increase resources.
• Improved Urlmon resiliency when receiving incorrect Content-Length for a PeerDist response.

Windows 10 Local Account - Administrator revisit

 Several posts on the threat of running every day access on any computer system with Administrator rights and privilege. 
 If you have used your Windows PC for awhile, you have a LOT invested in that account name with those dangerous rights and privileges. eMail, folders, many many items. 
 So just removing administrator as an account type can not be done until a replacement account with Administrator rights and privileges is created.
 You want that new Administrator account to be a local account, not a Microsoft account.
 Microsoft has made it more and more difficult to create a new local account.
 The following is a technique to create a local account as of this post.
 You will need to run as an Administrator to use these steps - yet another reason to only use Administrator for tasks that require Administrator rights and privileges. As soon as the task is completed successfully, log out of the Administrator account.

 As an administrator use the START button, then Settings, then Family & other users.

Use the Add someone else to this PC to get this screen

Then enter the username, a strong passphrase, and answer the 3 security questions. I suggest using a username that does not hint at being a power (administrator) user is creating a replacement administrator user. If creating a local account for another user use a name of your or their choice.

Quite Easily Done  QED

Note:  If needed, you may consider disabling the network. Turn off Wi-Fi, pull tne Ethernet cable or similar.

Robo calla? Robo Revenge

 Have a dislike for Robo calls? 

 There are apps that block KNOWN robo call numbers, keeps the list updated, answers the call with amusing (to the called party) responses "Hang on sweetie, I'm on another line"  then ties up the robo caller's line until they hang up. 
 Problem is they are apps, so they do not work on land lines. The list changes often, no real satisfaction to the called party, ...

 A new proposed app: DoNotPay proposes Robo Revenge. The name may change.
The idea: the caller answers the call, listens to the pitch, then responds with a one-time credit card issued for this particular call and transaction. The credit card belongs to DoNotPay. Once the caller's company completes the transaction DoNotPay has the transaction details on the company. DoNotPay then helps the called party file a suit against the company with an automated process to create demand letters, court filings, etc. Each successful suit can bring a $3000 fine to the called party under the Telephone Consumer Protection Act (TCPA) - a law already passed by congress so no awaiting any proposed legislative efforts. The app will add the called party to the DoNotCall registry if not already registered.

 The legislation is U.S. based so will only work with U.S. based companies.

 The DoNotCall registry does not work. I would think if this method works, the called number makes it onto a real "Do NOT call" list passed among robo callers very rapidly.