T wrote:

Hi All,

I had two interesting problem that I solved with Windows 10:

1)

a customer called me because her machine was slow and would not start
her programs consistently. You should have seen the
list of garbage she got for error messages.

Obviously, it was Fast Boot. Fixed that post haste.

But she had a weird problem with it sometimes asking for
her password. And she did not have one configured on
her computer. She really did not too.

She had the FREAKIN' Home edition, so I did not have access
the Users and Groups dialog. Users from Control Panel
had no provision to change the password. Users from the idiot
tiles would not change her password without the old password.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

DefaultUserName was set;
AutoAdminLogon was set; but
DefaultPassword was not.
Hmmmmm.

Okay, booted into Fedroa. chntpw said she had no password
I blanked in out any way.

She booted back up and SURPRISE! up popped a jammed One Drive
installation. I made quick work of that.

Fix a lot of other small things and she is now a happy camper.

2)

A customer had me remove a very old broken workgroup printer
and install a replacement. Part of the job was removing
the old printer and installing the new printer on five Windows
Nein-1903, oops Windows Ten 1903 Pro, computers.

The problem occured when I tried to remove the old computer.
Two went perfectly. Three would let me remove the printer
from Devices and printers, but the printer icon stayed
there, even after a reboot.

Hmmmmmm. Fussed with it a bit. This is what I came up
with.

1) remove the printer from devices and printers.

2) remove the printer from the registry. Double check to
make sure it was gone

3) go into the idiot tile setting for printers and remove it from there.
(Did not remove, by the way.)

4) go back into the registry and find where the printer had been
reinserted and remove it again.

5) go back into devices and printer and remove it again.
This time it removed.

Window Nein. What can I say.

-T

Please, this is Usenet and a tech support newsgroup, not to where you
publish your tweets, Facebook "what I did today" entries, or your diary.
I don't see your posting will have historical significance to anyone
else that may encounter similar problems. Seems more like another
tirade to lambast Windows 10.