(This is a rather technical post so feel free to skip this if the title means nothing to you)
I had a dilemma last night. I was linked to this great article by someone in ArsTechnica’s #linux on setting up SeamlessRDP to my VMWare Windows XP installation to achieve an effect similar to VMware Fusion’s Unity on Mac OS X. The problem is that I soon found out that Remote Desktop is disabled in XP Home Edition, only to be enabled in XP Professional.
It took a lot of digging around but I was eventually able to figure out how to get this enabled. So here is my guide on how to enable Remote Desktop in Windows XP Home Edition. Just a heads up that this was important to me because of RDP’s ability to launch specific applications for seamless integration into my Linux desktop, if you don’t need this and just want a full desktop window, one of the free VNC solutions might be better for you (TightVNC seems popular).
The first thing is to trick the installation into thinking that it’s actually XP Pro. I found this information here. Before doing this it might be best to make sure your install is already set up with Service Pack 2, etc.
- Navigate the Windows registry to HKEY_LOCAL_MACHINE/SYSTEM/ControlSet00X/Control/ProductOptions (where ControlSet00X is the one with the highest number) and delete the “ProductSuite” key.
- Create a new DWORD key in this same folder called “Brand” and set it’s value to 0.
- Reboot Windows. At startup mash F8 to bring up the boot options and choose “Last Known Good Configuration”.
After some hard disk churning you will be back to your welcome screen or desktop. You can then go to the System control panel and see that you now have a Professional Edition setup. This is great so far but unfortunately doesn’t actually install all those professional features.
Now I needed to get Remote Desktop to accept incoming connections.
I found this batch file on a forum post. It’s easy to follow; it basically creates a .reg file with the required keys, merges it, and does a reinstall of terminal services. After a reboot you should now see Terminal Services alive and well in the Services Administrative Tool. A “netstat -a” in the Command Prompt should show port 3389 as listening. At this point I was able to connect to my server but was getting disconnected immediately. After some more digging I found a replacement termsrv.dll that was actually from a Service Pack 2 beta but did the trick for me. Follow the instructions there or here (it must be replaced in safe mode). You might be interested in the registry edits mentioned in those posts as well for concurrent users.
I don’t know how much of this was necessary but after all this tinkering last night I am now able to Remote Desktop with success to my XP Home installation. Yay! One more thing… make sure you have a password associated with your Windows user!
Hi
I followed all of above suggestions. I now have Terminal Services a service, however, trying to start it gives an error saying “Access is denied” even though I’m logged in as Admin user. Do you have any ideas?
Shawn: that is interesting. Where are you getting the Access is denied error? In the Services Management Console or in the Event log? The best thing I could find in relation to the error was this article.
Hi Wade
It happens when I try to start Terminal Services. An alert box comes up with this message (Error 5 - Access is denied).
I’m logged in with Admin Privileges so it’s surprising.
Are you sure your firewall is setup to allow this. I’m not a computer pro, but if you have something like ZoneAlarm, be sure to have the IP address of the host (accessing computer) in the trusted zone list of the client (the accessed) computer.
Hi,
Thanks for this trick.
I also followed all what you’ve said, but I’m disconnected immediatly, even after changing termsrv.dll in system32 and dllcache (no problem for this). Port 3389 is listening. I can see the rdp tab, the screen is black and a message box says “the remote computer ended the connection” (it’s a translation, the message is in french). Do you have any idea to fix this?
Thanks in advance (and forgive my bad english)
thanks for the great howto, i’m putting together an archive for later use for myself (used the termsrv.dll trick for some xp pro installations many times before)
i’ve done everything right down to every step and am having the same trouble as the poster above, the proper termsrv.dll is installed and running (verified with process explorer), netstat -a shoes port 3389 is open, i try to connect and am disconnected immediately. if you happen to have any tips i would be grateful trying to get rdesktop going on my work laptop which only has home (now reporting as Professional of course)
I’m still tinkering around, i’ll post another comment if i run into some option that is still hindering the connections for myself and the above poster. Regards,
-ryan
I’m having the same problem as Baff. I’ve tried this on two different computers, but I am unable to connect to either one of them.
I’ve disabled the firewalls completely on them, but that doesn’t help.
Thanks for the feedback. I had the immediate disconnect issue as well when I was doing this and I believe it was the replacement .dll that fixed it. I will walk through this article again in a virtual machine and see if I maybe left something out. I will update soon.
I’m having the same problem as Baff and ted..
Smae problem here
Same problem here (Windows XP SP2)
any update?
Anything new about the disconnect issue?
Tried the same thing with my XP Home, but I also get disconnected. Another ting I noticed, the “Remote”-tab in system aren’t there. Tried with the sp-beta termsrv.dll, termsrv.dll from xp pro and the orginal termsrv.dll.
I just figured out how to FIX the DISCONNECT issue.
i spent 2 hrs playing but he it is.
I did everything like this post said then did this
Downloadedand installed devcon.exe from Microsoft. Its a command line device manager tool.
Then Run devcon.exe which will extract it.
Open a cmd prompt
Navigate to the i386 folder devcon made.
Type
devcon.exe -r install %windir%\inf\machine.inf root\rdpdr
after that i restarted then ran the batch file from before. then restarted again. FIXED
And it went right in to my desktop through Remote desktop
Please respond to let me know if it worked.
Mike
Heres the Devcon download
http://support.microsoft.com/default.aspx?scid=kb;en-us;311272
sorry
Thanks Mike.
the devcon solved the problem for me.
Works great.
Of course thank you Wade Menard for the great tutorial.
Thanks, worked great.
I would just like to add, that i used the termserv hack install after the bat file install so as to have multiple logins without affecting (booting off) any user. Also You must use passwords for all users, otherwise returns an error.
Here’s the (multi) termserv hack install link.
http://www.kood.org/terminal-server-patch/
Y not just use a 3rd party app ? (tightvnc etc)
I thought the original post explained why not tightvnc. Did you read it?
Thank you, Wade and Mike. Works nicely!
Perfect,
Thanks guys, it works great now, nice gift!
Bye
Had the same experience as Baff, but the “FIX the DISCONNECT” trick didn’t work for my Home Edition, maybe it’s some problem with localized version. I’m using a Swedish edition.
any suggestions?
Wow.
Seriously thanks guys!
I am posting this from my laptop which is connected to my XP home desktop. Genius.
okay, thanks first off! this did the trick for me!!
only thing, is there is no way it seems to LIMIT which users can rdesktop IN to the box. Any user with a login/password can. I am worried about this for security purposes, that’s all, from the outside… anything to worry about? what is best way to disable rdesktop when i don’t expect to be logging into it? just turn off the firewall port? or is there a quicker windows xp method?
thanks..
bill, you can use group policy to enforce that only administrators or the like can log on remotely. that is if you can find a way to edit group policy in home edition. i know in pro it’s gpedit,msc from run
Seems the original post works… The only thing didn’t mention is that you have to change the way user logon… After doing what the post said, the system were changed to autologin without a passwd… After changing the way user login (require a passwd), then you can connect from RDP.
I have done all of the above and can now connect via remote from my xp pro machine to the xp home machine, only problem is the xp home machine just logs traight on even with 2 users setup?
Any ideas?
Thanks
Thanks for a great solution to something that has bugged me for ages.
One more trick for those who want to remote desktop into XP Home with a blank password, since there is no editor for the local security policy there is a registry setting that can be changed to allow blank passwords:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\limitblankpassworduse=dword:00000000
Thanks to all for the information and comments. I needed to be able to control my XP Home machine with my MacBook since I have a lot of Windows software used to control my ham radio gear. I tried VMWare Fusion but they forgot to mention that Fusion doesn’t support serial ports, which I use for all radio I/O. This process works and I am VERY pleased.
So now this works great for me however when I log in to my desktop locally (on the actually system) It does not prompt me for my password anymore. Any Ideas?
Nevermind, to enable it so you have to log back into windows locally goto regedit
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
and change the “AutoAdminLogin”=”1″ back to 0
Hey - thanks for the info on how to get XP Home to allow remote desktop. I followed your plan - it worked like a charm.
This works, my XP home PC now accepts remote connections, thank you.
But strangely, ‘reboot’ logs into my account in without using the account selection screen, and does not require my password. I set-up two other non-Admin accounts, but don’t get a chance to select either at boot-up. I can only access these by logging off or switching user.
Another issue is that System Properties no longer has a remote tab.
Has anyone else seen this, or know of any solutions?
done everything upto Devcon section, but devcon command as shown gives a “devcon failed” return. any ideas
dudes get a clue, all you need to do is go into control panel, administrative tools, and services, and manually start the remote desktop sttings options!!
This is great info you’ve got here but maybe you could make it a little more understandable to the less tech savvy? such as maybe a screenshot or two? or maybe a little more detailed instructions on how to get to the registry and what to delete? Everything else is great!
Hi everything worked.
You DON’T need to replace the termserv.dll file. Skip that step. Here’s the instructions I used:
(1) Follow steps 1, 2 and 3 from the original post.
(2) Follow directions posted above on Dec 20, 2007 by Mike. Then reboot.
(3) Use the batch file. Then reboot. Magic!
The Auto Login Can be Setup by:
1) Click on Start on the windows task bar,
2) Click run
3) Type “control userpasswords2″ without quotes, click enter
4) setup as you require…
Thanks wade for the info, i havn’t tried the remote desktop setup yet…. been using net meeting remote desktop connection but the newer terminal services connection is the way forward!
Thanx Mike and Wade - I am using Remote Desktop on Win XP Home to send this note.
Awesome work!
Okay so Remote Desktop is working but it killed my IIS installation that I got from 2000 pro using
–> http://adamv.com/dev/articles/iis-on-xp-home
Does anyone know how to get IIS working again on XP Home?
Thanx,
John
hey, i press F8 when rebooted but nothing pops up my boot menu is F12 but it dosent mention, “Last known good configuration. please help
works great…thanks guys
After following these steps I can not see the remote tab?? Any ideas?
where do i get to the windows registry
i know what you mean ipc
can you make it simpler or else im going to go find a different place it took me three hours to find a site that actually told me
if it doesent say start from last good known configuration then press f8 again
Five Stars!
Thanks to Wade for the great “how to” and thanks to Mike and Anon for their input. I followed Anon’s 3 step process (posted Mar 5)and it worked perfectly.
Excellent and easy to use post. took less than an hour to set it up. Wow! Great work.
Now how about instructions to fix it for more than a single log in. I Work as a remote admin for a private, low budget firm with users who bought their pcs, and would love the ability to update the user’s pc while they are logged in and working.
I have been using tightvnc with great success but I prefer RDP.
Was really keen to try this. Went to regedit and when I tried the first deletion got a window titled ‘Windows - Licence Violation.’ Inside the winow it said ‘The system has detectyed tampering with your registered product type. This is a violation of your software licence. Tampering with product type is not permitted.’ Could not do any modifications without this window coming up and even when the change was shown, the changes could not be saved!
Anyone else had this?
@ Hiker
Feb 19th, 2008 at 11:18 pm
But strangely, ‘reboot’ logs into my account in without using the account selection screen, and does not require my password. I set-up two other non-Admin accounts, but don’t get a chance to select either at boot-up. I can only access these by logging off or switching user.
Another issue is that System Properties no longer has a remote tab.
Has anyone else seen this, or know of any solutions?
===========
same issues here…, is there any clue to solve this?
and is there any chance to switch back to “windows xp home” interface (specially in login screen and start button) without losing its terminal server capabilities?
ftf - thanks for the excellent post and comments! GREAT WORK
Great article, but like iPC said, it’s a little tech heavy for some of your sites less tech savvy readers.
Steps 1-3 and the devcon.exe along with the .bat file worked perfectly.
Thanks guys.
Okay great article and worked great too. My only problem now is how can I access the configuration pages of remote desktop server. In xp pro u can right click on the my computer and it will be the last tab on the top, however its not there after doing all the tricks mention above. Im not complaining that I cant connect bcos it does connect. I just want to know how I can get to the configuration pages.
Excellent! Worked as advertised.
Thanks!!!
Hi,
I followed your instructions and somehow, my 3389 port is still not listening. My windows is already XP home SP2, but I downloaded SP2 again and installed it because I didnot have the folder ServicePackFiles in my OS.
When I booted back in, I got an error saying something to the effect of cannot accurately authenticate the license. I think this happened because I had deleted ‘ProductSuite’ key, as suggested by you.
It was a very bad experience. I could not even log into safe mode since it didnot allow me in since I think it assumed my license was fake.
I spent a whole night figuring how to fix this - called up dell c/s, used xubuntu live cd, googled like crazy and finally gave up and was going to set my computer back to factory settings. Then wanted to try all that I had searched on google again this morning, and one of them fortunately allowed me to getinto safe mode, and now I am able get my computer back to form using an earlier restore point, two days old.
I regretted changing the registry without any backup. I tried accessing the windows registry using the linux xubuntu live cd, but didnot know what to reset it back to, and that made things worse.
But finally it all worked out fine to get my computer back to square one. Still figuring out why my 3389 port is not listening.
am considering giving this a go, but before i do does anyone have any ideas how this will effect any ability to upgrade to sp3?
Thanks
Anyone dealt with XP SP3 yet? I tried the upgrade on an archived OS - looks like this broke my XP - getting a problem with activation after the SP3 upgrade - cannot log in. Can still access files remotely, no user interface, though. Can also boot into SafeMode, but it now refuses to allow modifying the ProductSuite and /or Brand keys in the latest ControlSet (ControlSet004 for SP3).
I have not been able to get it to work, but I upgraded to SP3 this morning and had the same issue….however I was able to recover and go back to SP2 with the a system restore. Unfortunately now I still can’t mess with the registry key to get a SP3 install as it gives me the same error in SP2 now! Oy!
I had the problem with not being able to log in after upgrading to SP3, I was about due a reinstall so got round it that way. I upgraded to SP3 and then activated the RDC hack which works fine, but now I can’t get anything from Windows Update, I assume because Windows now thing it’s XP Pro but the license key is for XP Home. Tried to change back to Home, including using a tool called Mode Switch-this claims to have changed the product type but after rebooting it’s still Pro.
Will be looking into this more, oh yea came up with the “not allowed to modify the registry” message too
Another note. If you’ve unwittingly installed SP3 and want to undo the SP3 install, you can boot into safe mode (F8), - Fire up the control panel, open “Add or Remove Programs” - Make sure the “Show Updates” box is checked - Uninstall (Remove) “Windows XP Service Pack 3″ from the list…
Update, I think I’ve got this cracked with SP3, so far everything seems to be ok but no guarantees this works perfectly…
Firstly, a list of things:
WinModeSwitcher (http://www.filewalker.de/blog/details.php?id=13\)
The batch file from OP (http://geekport.com/files/enableterm.bat)
Patched Termserv.dll (http://sig9.com/articles/concurrent-remote-desktop)
Devcon mentioned in Mike’s post (http://support.microsoft.com/default.aspx?scid=kb;en-us;311272)
Ok first things first, I started with a vanilla XP Home SP2 install which I then upgraded to SP3.
Next up, run WinModeSwitcher and change from XP Home to XP Pro, apply and restart.
Run the batch file, restart and enter Safe Mode.
Extract patched termserv.dll into /WINDIR/system32 as described in OP and restart into Windows.
Extract Devcon and run path from Mike’s post above.
Restart again and you should have Remote Desktop access.
The main annoyance for me the first time I did this was having changed from XP Home to Pro via Wade’s registry edits, SP3 blocked me from changing back to Home in the registry, with the result that I was blocked from Windows Update because, I suspect, my product key was for Home not Pro. But with WinModeSwitcher, one can stay in Pro mode to enable Remote Desktop, but by changing back to Home and rebooting, Windows Update *APPEARS* to work ok, although Remote Desktop doesn’t.
Oh well, not a perfect solution, but works ok if you don’t mind the rebooting to get updates. Let me know if you have a go at this, if you get stuck at any point with not being able to connect etc, check Remote Desktop is allowed in the Windows Firewall, and if in doubt-give it a reboot
Update to my previous post, it appears that Windows Update is working OK when I am in Pro mode, just installed IE7 ok which wouldn’t install when I changed to Pro with Wade’s registry edits.
Thank you everybody here.
I wanted to undo the registry edit using the software WinModeSwitcher. I did it by first upgrading to XP pro and then come back using the same software. I also did many things including system restore and also registry edit which did not work. However, I do not know if those things had anything to do with my success. But upgrading and then downgrading were the last two things I needed to do.
I want to thank everybody here, I sincerely do… but at current time, I have nothing to thank them for, because frankly nothing I’ve done so far has worked.
I’ve tried every fix in the book thus far, and for some reason, everything is just fine until I have to add the Terminal Services… because the Remote tab under System Properties automatically disappears everytime I try the fix. I still haven’t a clue as to what could be (and obviously is) wrong, but I’ve tried everything and have been rewarded with nothing, and… well, let’s face facts; I’m lost.
Hi Greg,
With this workaround, you won’t see the remote page again. However, the remote desktop “mysteriously” works (if you have followed all the steps).
Dear Hadi:
I tried them all, and a few minutes after each trial I had a friend of mine try connecting through RDC after each fix, but it said the connection on my side wasn’t enabled, so he couldn’t get in.
Personally, I’m through with tampering with the registries. I think I’m just going to get RDC off my Windows XP CD tonight… and if that fails, then I’ll try these again.
Thanks for the support though, Hadi.
i don’t see remote tab in system properties, can anyone help me.
after trying, all the steps, I still get the disconnected message. =/
YES GOT IT TO WORK! THX MAN THE TUTORIAL ROCKS! =D
Anyone know how to put the ProductSuite regkey back to how it was?
I need to know how to rollback temporarily as well, so I can install SP3.
Thanks.
Works fine in SP3 for me, that is, no license problems. Windows Update still works fine etc. The termserv.dll is loaded and being used by Windows so I assume that’s working. The port is being listened on.
I’m getting the disconnected problem, but I’ve just installed the RDPDR driver as Mike documented and so hopefully it’ll work.
It works! But you should know that the “concurrent connections” termserv.dll may not be needed as noted above, but if you use multiple user accounts it may be useful.
However, it will still automatically dump you to the logon screen locally if you sign on remotely with the same account you’re using locally. Concurrent local/remote only works if you use different accounts for both. Which makes sense, since logging on remote allows you to access programs you were running locally, and because RDP is designed differently (ie it allows you to set different resolutions etc when connecting remotely) it can’t really let you control the same session remotely and locally like VNC can.
THANK YOU! it works like magic!!
Is it possible for any of you geniuses to take all of the above replies and boil them down into one “step by step” instruction for non-techies like myself. I’d like to do this but I am clueless.
This works great on my Win XP SP3 system, but I would like to set up a limited account for a friend (meaning a non-administrative user) and it appears only those accounts with administrative rights can log in. Is there a Registry entry or something that I can add to a User’s account to allow remote access (please don’t say Group Editor as I don’t have access to those files in XP Home).
What’s startup mash though? Is it necessary to hit F8?
Startup mash just means hold down F8 while booting to get into Safe Mode.
When i try and run the devcon.exe, the cmd window just opens and closes real quick. Anyone know what this could be?
I followed the steps but I get confused sometimes
This is what I did (as said by most replies)
followed steps 1-3 from the guide, then followed mike’s steps of extracting the file, which created the file “i386″ inside is the same file (Devcon.exe) but it just opens then closes in a spilt second…
I then ran cmd, navigated through the file and then typed what was said but it came up with the following message
“Device mode created. Install is complete when drives are updated…
updating drivers for root/rdpdr from C:\windows\inf\machine.inf.
devcon.exe failed.”
Any help?
BTW mike, which .bat file do you say you run again? the “enableterm.bat” from the guide?
Thanks for your help people
btw im using windows xp home edition sp3
I checked netstat -a and it has port 3389 as listening…
BTW2: I managed to get the cmd to install the devcon.exe on the path provided by mike… but its still not working :<
Awesome thread. I have consolidated the information above into a step-by-step guide here.
Thanks, Wade, for a fantastic and useful post which sparked an even more useful thread. Also, thanks to Mike, Anon, and Alex S. for their contributions to this guide, as well as everyone else for posting their experiences and issues, which made this guide possible.
Here goes:
1. Navigate the Windows registry to HKEY_LOCAL_MACHINE/SYSTEM/ControlSet00X/Control/ProductOptions (where ControlSet00X is the one with the highest number) and delete the “ProductSuite” key.
2. Create a new DWORD key in this same folder called “Brand” and set it’s value to 0.
3. Reboot Windows. At startup mash F8 to bring up the boot options and choose “Last Known Good Configuration”.
4. Download and extract “devcon.exe” and follow these steps:
(Devcon.exe can be found here: http://support.microsoft.com/kb/311272)
It is a self extracting zip file.
Run it by double clicking it.
When you run it, you will be prompted for a location to unzip it.
Type “c:\devcon” in the textbox and uzip it by clicking the “Unzip” button.
When it is done, close the self extractor screen by clicking the “Close” button.
5. Open a command prompt by going to the start menu and selecting “start->run” and typing “cmd” in the textbox and clicking “Ok”. You should see a command prompt. Leave it open.
6. Go to my computer, double click the “C:” drive, then double click the “devcon” folder, then double click the “i386″ folder. You should now see a file called “devcon.exe”. This file is different from the first devcon.exe. This one is NOT a zip file.
7. With your right mouse button, drag this “devcon.exe” from the folder to the command prompt window that you left open before, and drop it. You should now see something in your command window like “c:\devcon\i386\devcon.exe”, with quotes around it.
8. At the end of that line in the command prompt window, after the last quote, type a space, then type “-r install %windir%\inf\machine.inf root\rdpdr” (without the quotes).
The command line should now look like this:
“c:\devcon\i386\devcon.exe” -r install %windir%\inf\machine.inf root\rdpdr
9. With the cursor at the end of that line, hit the “enter” key.
Patiently wait until it finishes and the command prompt returns.
10. Reboot normally.
11. Download the batch file located here: http://geekport.com/files/enableterm.bat
12. Double click the file to run it.
Patiently wait until it finishes and the command prompt returns.
Note: In case that batch file link does not work for some reason, here are its contents:
@echo off
echo Windows Registry Editor Version 5.00> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService]>> c:\TS2.reg
echo “Start”=dword:00000002>> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]>> c:\TS2.reg
echo “AllowTSConnections”=dword:00000001>> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]>> c:\TS2.reg
echo “fDenyTSConnections”=dword:00000000>> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]>> c:\TS2.reg
echo “fAllowToGetHelp”=dword:00000001>> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]>> c:\TS2.reg
echo “AllowMultipleTSSessions”=dword:00000001>> c:\TS2.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]>> c:\TS2.reg
echo “AutoAdminLogon”=”1″>> c:\TS2.reg
%windir%\regedit.exe /S c:\TS2.reg
echo [Components] > c:\bootlog~.txt
echo TSEnabled = on >> c:\bootlog~.txt
sysocmgr /i:%windir%\inf\sysoc.inf /u:c:\bootlog~.txt /q
DEL /Q c:\TS2.REG
DEL /Q c:\bootlog~.txt
exit
If you paste that into a notepad file and save it as “enableterm.bat” you will have the file you need.
13. Reboot normally.
14. Reboot again before you decide if you need to continue with the steps below, since the “AutoAdminLogon” setting applied in the batch file sometimes automatically resets itself after another reboot.
If you are no longer being asked for a password when you login, follow these steps:
NOTE: To use remote desktop, passwords must be enabled.
NOTE: Be sure you have an administrative account and you know the username and password to it before you proceed.
1. Click on Start on the windows task bar.
2. Click run.
3. Type “control userpasswords2″ without quotes and click enter.
4. Check the box that says “Users must enter a user name and password to use this computer”.
5. Click “Ok”.
6. Reboot normally.
You are done. You should now be able use remote desktop to connnect to the computer you did this stuff on.
Regards,
Jesse
I’m still getting the devcon.exe failed… any ideas? I’m typing it in exactly as posted! Do I need to be in safe mode when doing the devcon.exe command?
Jesse Chun’s instructions needs a reboot normally after the last good config reboot of step 3 for the devcon step not to fail.