Some Notes on the Machines

Create a shortcut to this:

explorer.exe shell:::{3080F90D-D7AD-11D9-BD98-0000947B0257}

and name it “Show Desktop”. When double-clicked, it will minimize all applications and show the desktop. This was standard in 7 and before. You can pin this icon to the Taskbar, to the Start menu, et cetera.

The icons which were used in the “Start Menu” in 7 and before, are still present in Windows 8 through 10, though they are hidden. At the machine level, they are here:

%SYSTEMDRIVE%\Users\All Users\Microsoft\Windows\Start Menu\Programs

At the user level, they are here:

%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs

This error often occurs when a longstanding Windows Server network is given a much newer domain controller. The WINS records embedded in DNS, don’t work anymore; when you try to delete them or change them, you get the error message in the title of this article.

The best thing to do, is PowerShell:

Remove-DNSServerResourceRecord -ZoneName dns_zone.local -Force -RRtype "WINS" -Name "@"

Try that (substituting dns_zone.local for your LAN DNS zone!), then right-click on the zone name, choose “All Tasks” and then “Reload”, then press F5 for refresh. The error-causing situation will go away, you can then reconfigure easily. If there are other zones, you’ll want to repeat for all of them. If there is a WINS record in a reverse lookup zone, the RRtype is WINSR instead of WINS, the result being something akin to this:

Remove-DNSServerResourceRecord -ZoneName 1.168.192.in-addr.arpa -Force -RRtype "WINSR" -Name "@"

Sometimes the actions above only take effect, and show up in the servers, if you reload and refresh (often both) the zones.

Currently, the only known way is this sort of effort:

Set-MpPreference -DisableIntrusionPreventionSystem $true `
-DisableBehaviorMonitoring $true `
-DisableRemovableDriveScanning $true `
-DisableScanningMappedNetworkDrivesForFullScan $true `
-DisableScanningNetworkFiles $true `
-DisableEmailScanning $true `
-DisableBlockAtFirstSeen $true `
-DisableIOAVProtection $true `
-DisableRealtimeMonitoring $true `
-DisableScriptScanning $true `
-EnableControlledFolderAccess Disabled `
-MAPSReporting Disabled `
-SubmitSamplesConsent NeverSend `
-PUAProtection Disabled

Try this, in administrative Powershell:

wevtutil el | ForEach-Object { "$_"; wevtutil cl "$_" }

Does not seem to have a web page of its own, it is linked from others:

http://aka.ms/diag_printer10

Very informative:

https://support.hp.com/us-en/document/c05195282

and linked therein, a printer matrix:

https://support.hp.com/us-en/document/c04658195

It is far from clear what is going on, but here’s what I think I know:

• Lots of services are being created in Windows 10, 2016, and 2019 fitting the descriptions below.
• Many of these, but not all, have names with “_a1b2c” at their right-hand ends, where the characters and numbers are what look like non-random machine-readable strings, five characters long so far.
• Many of these, but not all, have been svchost.exe items, not standalone services.
• There are a variety of service names associated, including (on just this one machine) CaptureService_b8bc7, “Clipboard User Service_b8bc7”, “Connected Devices Platform Service”, “Connected Devices Platform Service_b8bc7”, “CredentialEnrollmentManagerUserSvc_b8bc7”, and many more. Of the list in this item, only the last is a standalone service, not a svchost item.
• There are a variety of svchost item names associated, including BthAppGroup, LocalService, and UnistackSvcGroup. In particular, the UnistackSvcGroup items can be googled, but thus far, it appears not known for what they are used.

Some of these services cannot be deleted with the SC command; some can. If one changes permissions in registry items, they all probably could. But the question remains, what are they for, what are our valuable computing resources being taken for? Thus far, no one has reported anything not working when they are stopped and/or deleted. We may be looking at infrastructure Microsoft is laying in our own machines before our eyes, for new software they will send.

There’s an automatic “backoff” feature of Windows Indexing from Vista onward, which causes it to slow down and stop depending on other load. This can prevent Indexing from working altogether when load is high and/or searchable datasets are very big. To fix this, change this registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gathering Manager\DisableBackoff

to a numeral 1. You will probably have to change the owner of “Gathering Manager” to Administrators in order to do so. After this change is made, restart Windows Indexing.

These packages bundle configurations, even domain joins, and other items. Native to Windows 10:

https://docs.microsoft.com/en-us/windows/configuration/provisioning-packages/provisioning-create-package