Chris Spera Contact Information - Per Gabe Aul Tweet

I have the same issue with the disappearing ink (one note 2013 on Surface pro 3 build 9926). There is another thread on the feedback forums here discussing the same issue. Lots of people having this issue and it makes life REALLY difficult if you're trying to take notes in lecture.

In my experience and as is noted in the other forum post I mentioned above, I don't think the syncing is an issue. Ink still disappears if you disable sync for the notebooks. If there's anything I can provide to help fix this bug let me know because it's the one bug in Windows 10 preview that makes life really hard. Also any updates on the current status of the problem would be appreciated.

I know this report makes you really want the logs on this, and I'll get them to you if I can.  However, I'm trying to stand up a SQA program from scratch for a new company, and I'm a bit short on time.

Its fine, I understand. Good luck on that :)

We are investigating the bug. Sync isn't related to it.

-Mavis (OneNote Team)

Hello Mavis and the OneNote Team!

Thank you for undertaking this issue. I really do appreciate it.  I know its only been a day or two, but I was curious to know if there's been any progress on this issue?

Have you isolated a root cause?

All of the Notebooks in question are syncrhonized to OneDrive, and are NOT stored locally.  I was curious to know if synchronization might be considered to be a contributing factor or not.

Thank you again for all of your hard work.  It is GREATLY appreciated!

If you hit this state again, you should re-launch the app.

Yep, that´s exactly the only workaround for now. But sometimes it can recover itself from this state and only the "disappeared text" got lost, all the rest stays where it was. If I can do anything else for you don`t hesitate to ask.

you can always write me an e-mail  at p.burlet(at)hotmail.com

Mavis,

I've noticed this behavior in OneNote Preview, and the app can "recover," but the ink that was written while the app was in that "bad state" is lost. Ink written after that (i.e. when the screen "unfreezes," is saved.

Depending on the severity of the "bad state," the app will either recover, auto minimize and show a recovered app window when the window is restored, auto minimize and not recover (displaying only its splash screen when the app window is restored), or have a state so severe, that the Window won't restore, and you have to quit the app via Task Manager or, if possible, tap and hold the icon on the Task bar and then choose "Close."

I know this report makes you really want the logs on this, and I'll get them to you if I can.  However, I'm trying to stand up a SQA program from scratch for a new company, and I'm a bit short on time.