Windows 10: Keystrokes lagging, unless launch applications with elevated privileges

Hi


I have a new Windows 10 laptop (Lenovo Ideapad 720), logging in with an MS account (same account as my old Windows 10 laptop)


I've run all the windows updates, and run a BIOS update from the manufacturer, and throughout that process I've had a massive lag on keystrokes, to the point of making it practically unusable for anything that requires keyboard work.


When launching a cmd prompt with elevated privileges to run system diagnostics I noticed the problem went away inside the prompt.


This is repeatable with applications - if I launch two instances of excel - one with elevated privileges and one without - typing lags on the one with normal privileges and on the elevated one it's fine.


Any ideas what could cause this?


Thanks

Ciaran

:)

 

Elevated Privileges

What program?

Elevated Privileges in Windows 8 / 7

http://www.thewindowsclub.com/elevated-privileges-windows

Ways to Grant Elevated Privileges In Windows

http://www.windowsecurity.com/artic...y/ways-grant-elevated-privileges-windows.html

 

Never prompted to elevate privilege as administrator


OK, I tried Dinesh's tutorial. First, here's a list of accounts for my machine:





I held down Shift and rebooted, and got the WinRE splash screen. I was prompted to log in, with "Dan" my only option:





If I clicked on "Don't see your account", I got this:





Is it suggesting that "Dan" is an administrator account? Oh, that it were so... I went back, selected the "Dan" account, and it booted into command prompt. I then attempted the first of Dinesh's instructions:





Hello darkness, my old friend... "Access Denied."

Dan

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.