Since this sounds then like a Microsoft issue, my next suggestion is the Skype Support page at https://support.skype.com/en/skype/all/ I was going to suggest the Disability Answer Desk, but that page

That's honestly the sort of thing that would happen if the password is wrong or changed. Assuming the email address associated with the account still reaches you, you might try a password reset. I don

I just updated to 8.67.0.99 without incident, but mine signs in automatically. Let me know if this one resolves itself; I wonder if it's something like a busy Microsoft server that caused your sign-in

If you are not using my scripts, try maximizing and restoring the Skype window to get through that ChromeLegacyWindow moment. If you are using my scripts, this should be happening automatically, thoug

I think you're asking about the same issue: The ChromeLegacyWindow announcement occurs when Skype has been minimized.

I said I wouldn't, then I did... Skype script revision 178 is posted at http://www.dlee.org/skype/ This update includes the same sort of automatic fix that I put in the scripts for Microsoft Teams a f

Ah, "rumor" is what I called it because I only heard one report and not from a Skype author; no disrespect meant. In any case, see my next announcement; there is now a solution in place for JAWS users

Frequently discussed in various places nowadays, and it's a change in Skype 8.63 and is not due to Windows 10 2004. The workarounds are to tap Alt twice, tap Alt and then Esc, or use Windows+DownArrow

On hearing this morning that Skype 8.64, apparently in beta, also exhibits this issue, I filed the following comment for Microsoft via the "Report a Problem" item in the Skype Help menu; and I invite

This looks very much like a problem I've seen in Teams that was fixed there by now in Teams itself. The basic situation is this: The Skype accessibility information starts showing up in a different wi

What exact message do you get? I can't tell from that description if it's like, "This program is not signed and may harm your computer," or just, "This program may harm your computer," or something el

I think I found the problem: SLMan was not updated to use the new Skype script basename, because I forgot that it used one at all. Try installing SLMan from https://www.dlee.org/updates/jfw_slman.exe

If I get any further ideas, I'll let you know; but for now I don't have any. I have heard of this happening to exactly one other person with a set of scripts, though I don't remember which set. I've a

Is your JAWS set to use the same language for which you checked the ConfigNames file?

Compare your ConfigNames.ini section against the skype_directives.txt file that now comes with the scripts, to make sure the entries in the directives file are also in the appropriate section of your

That message is in my first category; it shows up when the download is not known by sites that rate downloads by perceived safety. Simply put, it was a new script release; so it was not "commonly down

I am concerned that people are actually disabling Windows Defender and possibly other protective software to download my scripts. The following is a bit technical and mostly aimed at getting technical

I doubt that last number means much to us, but that of course depends on the specific company/product etc. I don't know how to find specific builds by number nowadays. I haven't tried Ctrl+Shift+P sin

Yes, the subject says "six issues." Read release notes at http://www.dlee.org/skype#hist and download scripts from the download link earlier in that same document. The main issue fixed here is of cour

By now I have a diagnosis but not a solution. Short version: The problem resulted from my renaming skypeelectron.jsb to skype.jsb for some reason. If I rename it back and change ConfigNames.ini accord