Chris Spera Contact Information - Per Gabe Aul Tweet

Anonymous
2015-03-05T19:56:13+00:00

OneNote Team,

I can be reached via email at <PII removed> .  eMail me there, and I will shoot you more specific contact information, including a phone number, so we can chat.

Microsoft 365 and Office | OneNote | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

127 answers

Sort by: Most helpful
  1. Anonymous
    2015-08-09T18:43:07+00:00

    I'm wondering the same thing. I'm considering rolling back to 8.1 until a fix for this comes out, as my Surface 3 is used primarily for note taking in OneNote.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-08-09T01:50:16+00:00

    Mavis, any word on when the patch for OneNote 2013 should roll out? Many users are still reporting problems (see http://answers.microsoft.com/en-us/insider/forum/insider\_office-insider\_onenote/inking-in-onenote-on-surface-pro-3-disappears/b6c5f168-f4dd-48ef-996b-8b933a28da9c?page=10&tm=1439084697299&auth=1) and I am close to downgrading my Surface 3 to Windows 8.1 since OneNote on Windows 10 is unusable with the pen.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-07-24T19:03:48+00:00

    I understand. The O16 preview version is more robust to that bug. We plan to update the O15 client in August with a possible fix that could avoid this bug.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-07-17T09:20:29+00:00

    I've just installed the windows 10 10240 release and run it with office 365 (onenote 2013 up to date), and have found the disappearing text to be such a pain that I had to roll back to 8.1.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-06-16T19:55:20+00:00

    Hello Mavis, I'm on office 2013 with exchange so not sure 2016 is a option at this point

    Nevile,

    I was in the same boat with Office 2013 and Exchange 2010, but my provider upgraded my exchange server to Exchange 2013 and enabled auto-discovery, and that's how I was able to get past my initial issue/ problem (which, BTW, was ugly).

    Check to see what Exchange version you're provider/ office is using; and if auto discovery is enabled.

    Was this answer helpful?

    0 comments No comments