2020. 3. 3. 00:05ㆍ카테고리 없음
Disclaimer: I am not liable for any damage to your system. Please use the scripts/instructions at your own RISK.For the past year, I've been having issues with the type cover:. Suddenly disconnecting. Not getting detected when I use tablet mode or after sleep/shutdownTypically, when this happens and no troubleshooting works (even the 2 button shutdown), my fix was to drain the battery (until it wouldn't turn on) then charge the device - the type cover consistently got detected using this method.After some research, I managed to find a breakthrough which was to use DevCon exe from Microsoft. So here goes:.
Devcon Install Inf Package
Type Cover is not detected. Run the script below (create a.bat file from note pad if you want -but you need to setup a shortcut with Administrator rights)devcon Remove USBROOTHUB30devcon Rescandevcon Rescan USBROOTHUB30devcon Remove VID045Edevcon Rescandevcon Rescan VID045EYou can add a Restart Code here if you want: 'Shutdown -R Now 'At this time, if the script was successful, you should see the type cover keyboard light up. If it didn't, try removing then reattaching the keyboard, it should light up. If you did not add the restart script, restart the system nowNotes:. I have the Surface Pro 3, so the USB Root and VID045E device/hardware ID might be different in the SP4.
I haven't managed to find a way to detect/setup the keyboard using the script - IF ANYONE HAS A SCRIPT FOR THIS PLEASE DO SHARE =)Requirements:. DevCon.exe (google to get the exe. I recommend using the official WDK from Microsoft but it's 600MB). Add DevCon.exe to your PATH (in environment variables). Courage. I am not sure if the script will damage any hardware but I am desperate as even the 2 button shutdown does not work for me.EDIT: The code 'devcon restart USBROOTHUB30' might have done the trick. After running this, I remove the cover and attach it again and it seems to work - no need for a restart =).
When answering a question please:. Read the question carefully. Understand that English isn't everyone's first language so be lenient of badspelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, oredit the question and fix the problem.
Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it.Provide an answer or move on to the next question.Let's work to help developers, not make them feel stupid.