|
|
Link or it didn't happen. Unless this is hyperbole, in which case, well done 
|
|
|
|
|
Hi, Jon, it's a direct quote from an OP's response on a current QA question.
I don't link to it because I do not want to "name and shame."
cheers, Bill
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
Oh, wow. That's... interesting 
|
|
|
|
|
|
It seems so meta it almost feels like a troll.
modified 15-Apr-18 4:21am.
|
|
|
|
|
No idea what that feels like myself. 
|
|
|
|
|
OG's response to a Q&A post was also sooo classic:
You do realise what ExecuteNonQuery does?
Hint: think about the "Non" part ...
Why is it that CP seems to collect the worst of Q&A Q's? I don't see this crap posted on SO, for example.
|
|
|
|
|
Do any of you ever attempt to log onto your win10 computer and it tells you that you are typing an incorrect password but you know you are not?
I'm having a wifi adapter problem and at times I leave my computer and it goes offline and then the machine will tell me that I'm using an incorrect password even though I am not.
Just curious if others are seeing this.
I also have a lot of these in my Event Log:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
EDIT
I searched for that CLSID and found a youtube that really does explain the problem.
How to fix Event ID 10016 DistributedCOM ShellServiceHost errors - YouTube[^]
modified 14-Apr-18 17:18pm.
|
|
|
|
|
raddevus wrote: and it tells you that you are typing an incorrect password but you know you are not?
If you send me all your accounts and their passwords, I can make sure that that error message is actually accurate. 
|
|
|
|
|
Marc Clifton wrote: If you send me all your accounts and their passwords
The Lounge is always so helpful.
userid: mycomputer
password: passsword1
I'm awaiting the fix. Thanks so much.
|
|
|
|
|
raddevus wrote: passsword1
There's the problem! You misspelled "password"!
|
|
|
|
|
|
do u have all the latest windows updates etc? and maybe u should try to restart the router once
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Thanks for chiming in on this. I do have all the latest updates.
There are definite issues that have only occurred with my laptop since upgrading to win10 -- previously ran Win8.1.
Recently I have suffered with a wifi adapter issue related to win10 drivers and win10 precludes me from rolling back to a driver that worked in the past. win10 controls everything. quite annoying.
|
|
|
|
|
raddevus wrote: Recently I have suffered with a wifi adapter issue related to win10 drivers and win10 precludes me from rolling back to a driver that worked in the past. win10 controls everything. quite annoying.
Yep,
Windows will use the date and driver version to make this decision... if you attempt to 'roll-back' and then Windows locates a more recent driver then you may end up having the most recent driver reinstalled.
It takes less than 60 seconds to remove it from the driver store. Open a Command Prompt and do:
dism /online /get-drivers /format:table
Locate your Wifi driver in that list. If you are unable to locate the driver in this list then you can also get a more detailed list by doing:
pnputil.exe /enum-drivers
Once you locate the Wifi driver then do:
pnputil /delete-driver [INF FILE NAME]
Reboot and reinstall your old driver. Also... if your Intel Wireless driver has been published to 'Windows Update' then make sure you are not connected to the internet when you do this. Otherwise the latest driver will be downloaded from Windows Update.
You should probably just keep the latest driver.
Btw are you still having problems with this Intel Wireless driver[^]?
I never mentioned this... but Intel will probably blame it on your "INSYDE Corp" BIOS. Make sure you have the latest BIOS. Even if you do have the latest BIOS... reboot and go modify your power management settings. Go in there and look for an 'S4'[^] and try disabling that. try running with that for a week and see if your problem goes away.
Also... go into Windows Device manager and right click on your wireless card in the list. There should be a setting on one of the tabs to prevent the wireless card from entering the low power state during sleep/hibernation.
Think outside the box... you don't really need to mess around with BIOS and drivers... you can just instruct the operating system to not allow your wireless driver to enter the low power state.
Best Wishes,
-David Delaune
|
|
|
|
|
Thanks for the details. I will try it out.
|
|
|
|
|
raddevus wrote: I will try it out.
Good. I think abut 1000 people are waiting for you to finish 'Practical Electronics For Makers' part 4.
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: I think abut 1000 people are waiting for you to finish 'Practical Electronics For Makers' part 4.
Oh, wow. Thanks very much for letting me know. That's really nice.
I got the flu and got knocked down for about 10 days now. I'm just getting over it now.
Thanks again for the encouragement.
|
|
|
|
|
Have you tried unplugging it then plugging it back in?
|
|
|
|
|
This might be completely unrelated, but it's food for thought anyway.
There is one common username/password I prefer to use to log onto my different machines. However, I have a laptop (a netbook), on which I cannot use this password with some Linux distribution (I forget which--maybe some version of Lubuntu, because it's supposedly low-overhead) because it simply refuses to let me type a specific key (lowercase 'm') when attempting to log in.
No "." character gets added in the password field, unlike every other key for the password. The button isn't broken; when I initially entered it during the account creation, the key was functional, and at no other time does the key ever misbehave. For example, in any plain text field, if I press 'm', there's no problem. I even reinstalled the OS, after I realized what was going on, and paid close attention to the password field as I entered the password when (re-)creating the account. It gets accepted at that time. Yet once I'm at the actual login screen, it's rejected.
Being a laptop, some of the keys serve double-duty and are used as the numeric keypad as well - 'm' gets assigned to '0', and the NumLock key is used to switch between numbers and letters. However, no matter how many times I press NumLock at the login screen, pressing '0'/'m' registers no additional keystroke.
|
|
|
|
|
That's a very good point about the way keys can misbehave. Thanks for giving me more ideas of what might be happening.
|
|
|
|
|
I've also seen it where a key is misbehaving. Especially on laptops, I've seen stuck alt or shift keys, etc.
One thing that happens on our iMacs is that if you hit space to wake the computer up and turn on the monitor to show the login page, it actually puts a space before your username and won't log in properly. It's really hard to see because the text is barely moved over.
|
|
|
|
|
This is probably not related to your problem at all, but I will bring it up anyway as somebody else may have some idea about what caused it.
When I travel on holiday I don't take my laptop as I don't need it. I just take an ancient HP netbook running XP, mainly to back up my photos each night and check my email via webmail.
I went to the Philippines for about a month over Christmas, and imagine my chagrin when it told me the password was wrong, yet I had been using it for years - I only use this HP for holidays and the only things on it are my photos which are removed as soon as I get home.
On a close examination of the input box I noticed that the *s appeared to jump around a bit, and established that the keyboard was producing the correct letter, but occasionally was putting the nth character at the start of the password. I later established that this was pretty random - it might happen, it might not, it may chose a different character each time, it might not.
The only solution I found was to use the 'impaired' keyboard, and use the mouse to click on each character in turn, which always worked. Once logged in, the keyboard behave normally.
Go figure!
|
|
|
|
|
Interesting story. Thanks for sharing.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
