Hey all, Recently (post 1903 update), my Surface Book 2 screen started flashing black every time I touch my Surface Pen to the screen to ink something. It works just fine if I'm using the Pen as a cursor (IE moving/closing windows, etc all work just fine) and if I'm using the pen to ink in a Win32 app. What I've tested in so far: OneNote UWP -- flashes when inking MS Whiteboard -- flashes when inking MS Sticky Notes -- flashes when inking OneNote 2016 -- works just fine I've run the Surface Diagnostic Toolkit, re-installed the Intel UHD drivers, installed the latest Surface Firmware, and run Windows Update, all to no avail. I'm running W10 1903 Build 18362.175 on a 13in Surface Book 2 i7-8650U. Has anyone run into this issue before, or have any thoughts on what I should try next? I haven't tried a different pen since I only have the one, but that was my next thought.

Surface Book 2 here with the i5 and intel 620 graphics - with MS help I rolled back the driver for the intel 620 - it literally has a setting that says "roll back" below is what I copied from that chat session " On your keyboard, press the Windows logo key and R at the same time to invoke the run box. 2) Type devmgmt.msc and click the OK button. 3) Expand the Display adapters branch. Right-click the Nvidia graphics card device and click Properties. 4) Click the Driver tab. Then click Roll Back Driver." not tried woth one-note but normal inking ok -

I fixed this in my environment. Traced it back to a MSFT security baseline GPO Computer | Windows Settings | Security Settings | Local Policies | User Rights Assignment | Increase Scheduling Properties. Thanks dervturbo for the fix! I'll make it clear what we needed to do to fix it Run gpedit.msc In an enterprise environment, get your Group Policy admins to make the change for you On Windows 10 "Home" edition, gpedit is not available by default Navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment : " Increase Scheduling priority " 3. Ensure both " Administrators " and " Windows Manager\Windows Manager Group " are in the list. (If they're not, add them. You can copy/paste without the quotes) 4. Reboot This brings Windows back to its intended defaults (which changed somewhere along the way). Tell your IT admins to reference the highlighted yellow box on this article: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/increase-scheduling-priority#security-considerations

Thanks rpertusio, I found when i restore it includes the value and fixes it, although after an hour it resets to this with this error. Any Ideas?

Thanks rpertusio, I found when i restore it includes the value and fixes it, although after an hour it resets to this with this error. Any Ideas? Sure. Change the value, then immediately do a " gpupdate /force " at a command prompt. If it immediately breaks after the command is complete, then you have a Local Policy or Group Policy that's coming back to enforce it. -Ryan

Yes, i do seem to have a policy applying it. Its called moe how can i remove it without loosing the ability to login to the domain? I cant acually change it, only an windows update fixes it. And then it reverts and when i try to edit it, it has the error at the bottom of the picure before.

Surface Book 2 Screen Flashes Black when inking in UWP Apps

Anonymous

Hey all,

Recently (post 1903 update), my Surface Book 2 screen started flashing black every time I touch my Surface Pen to the screen to ink something. It works just fine if I'm using the Pen as a cursor (IE moving/closing windows, etc all work just fine) and if I'm using the pen to ink in a Win32 app. What I've tested in so far:

OneNote UWP -- flashes when inking
MS Whiteboard -- flashes when inking
MS Sticky Notes -- flashes when inking
OneNote 2016 -- works just fine

I've run the Surface Diagnostic Toolkit, re-installed the Intel UHD drivers, installed the latest Surface Firmware, and run Windows Update, all to no avail. I'm running W10 1903 Build 18362.175 on a 13in Surface Book 2 i7-8650U.

Has anyone run into this issue before, or have any thoughts on what I should try next? I haven't tried a different pen since I only have the one, but that was my next thought.

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

57 answers

Anonymous

2020-05-17T12:20:46+00:00
Surface Book 2 here with the i5 and intel 620 graphics - with MS help I rolled back the driver for the intel 620 - it literally has a setting that says "roll back" below is what I copied from that chat session

" On your keyboard, press the Windows logo key and R at the same time to invoke the run box. 2) Type devmgmt.msc and click the OK button. 3) Expand the Display adapters branch. Right-click the Nvidia graphics card device and click Properties. 4) Click the Driver tab. Then click Roll Back Driver."
- not tried woth one-note but normal inking ok -
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-19T20:11:41+00:00
I fixed this in my environment. Traced it back to a MSFT security baseline GPO

Computer | Windows Settings | Security Settings | Local Policies | User Rights Assignment | Increase Scheduling Properties.

Thanks dervturbo for the fix!

I'll make it clear what we needed to do to fix it
1. Run gpedit.msc
  
  In an enterprise environment, get your Group Policy admins to make the change for you
  
  On Windows 10 "Home" edition, gpedit is not available by default
2. Navigate to:
Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment : "Increase Scheduling priority" 3. Ensure both "Administrators" and "Windows Manager\Windows Manager Group" are in the list. (If they're not, add them. You can copy/paste without the quotes) 4. Reboot

This brings Windows back to its intended defaults (which changed somewhere along the way). Tell your IT admins to reference the highlighted yellow box on this article:

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/increase-scheduling-priority#security-considerations
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2020-06-06T01:56:00+00:00

Thanks rpertusio,

I found when i restore it includes the value and fixes it, although after an hour it resets to this with this error. Any Ideas?
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-06T02:29:02+00:00

Thanks rpertusio,

I found when i restore it includes the value and fixes it, although after an hour it resets to this with this error. Any Ideas?

Sure. Change the value, then immediately do a "gpupdate /force" at a command prompt. If it immediately breaks after the command is complete, then you have a Local Policy or Group Policy that's coming back to enforce it.

-Ryan
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-06T02:37:52+00:00

Yes, i do seem to have a policy applying it. Its called moe

how can i remove it without loosing the ability to login to the domain? I cant acually change it, only an windows update fixes it. And then it reverts and when i try to edit it, it has the error at the bottom of the picure before.
Was this answer helpful?

0 comments No comments