OneNote Web Clipper will not sign in

Hi all. possible solution. I use a hotmail account with one note and use it for mobile, desktop and browser. I logged in with my browser when I could not get the one note clipper to show a new section I had created. I disabled the extension in chrome, reenabled it, closed a one note error pop up dialog box that was not visible until I hovered over chrome on the taskbar, logged into my hotmail in the chrome browser and then tried the clipping and it clipped the web page article I was viewing successfully!! The new Microsoft Edge is not too bad and you should try that as well. I was an Edge and IE hater but they've made an effort and its not too bad.

It's not that I do not use Edge.

I like it much better than IE or even Chrome which I never use but my preferred everyday Browser is Firefox.

I must also admit I don't use Hotmail or any other service but host my own Mailserver.

But thanks for the Tips, I am certain it will help someone.

How does a company like MS 'break' something like this that has been working for years? And why is it taking so long to fix?

I reached out to the program manager and here is a part of the reply "The team is investigating now.  They've confirmed the behavior you are seeing, but not the cause yet." Obviously, there is a serious problem that is taking a while to resolve and test. In the meantime, I bought "Fireshot" as an interim fix until MS fixes one of my favorite tools. It is a close second to NoteClipper. Life goes on and I have work to do, at 74 I have more work days behind me than in front of me and I have a lot to do.

As a career long s/w developer, I find it highly disturbing that

1. MS engineers don't log and mark their changes (internally), and
2. MS engineers can't find and fix bugs THAT THEY INTRODUCED VIA THEIR CHANGES very quickly. If they had decent change management procedures, they would be able to zero in quickly or, at minimum, be able to roll back to the previous version.
3. MS doesn't provide release notes when they do a module update, and
4. MS won't communicate the current status to their users on a regular basis.

This is what a monopoly and intense hubris provides.

I hope their program manager AND their development team all have red faces, but I doubt it. They are way too cocky.

Why do I say that so confidently? Because change management Best Practices have been around for over 30 years (plus anyone with common sense and a tad of experience can figure it out themselves). If they weren't cocky, they would be using them.

Because they are too cocky to think Change Management Best Practices apply to them.