Wednesday, April 7, 2010

Starting LogMeIn in Safe Mode with Networking

The trouble with having remote access to a computer is that most of the time it fails miserably when you really need to fix that computer. For instance, you can't connect through LogMeIn to a computer started in Safe Mode (with Networking).

I did a test today and if you start a PC in Safe Mode with Networking and you go to the Services application, if you try to right click and start the "LogMeIn" process, it will say it can't be started in safe mode. Bummer.

Thankfully, there is a solution for that - you add the service to the trusted list of processes for Safe Mode, and presto, you can start it.

You just need to add a key in the registry using this rather obscure command (start a new command prompt), and you are almost done:

reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Network\LogMeIn" /VE /T REG_SZ /D "Service"

(one line). The output should be like in the next picture

Now, the process can be started in safe mode (with networking) by right clicking it in Services and selecting "Start". Don't worry if the process takes a long time to start or if it generates an error saying that it takes too long to start. Even in this crippled state you can log on remotely and do your thing.

This trick is persistent across reboots. The next time you get in Safe Mode, LogMeIn will be started on boot (bootup may be slower, though). Beware, there is a risk - if for some reason LogMeIn is the cause for Windows not starting in the Normal boot, it will also hang in Safe Mode with Networking!

 Good luck!


Mike and Summer said...

YOU ARE A GENIUS!!! PROPS MY BROTHA, you totally saved me. I had an Administrative session with Join.ME to a windows server 2008 and I have no way to get back into the system. It freezes on normal boot and I only had this one chance to get into the system. Now I have LOGMEIN to the rescue!!!

chrisrand said...

This should be implimented in to LMI right away.

It just saved me the hastle of having to ship an infected computer, fix it and then sending it back.

I can't say thank you enough!!!

And to think, your the only one in the world who has shown the rest of us how to do this.

Would it be cool if I share this information elsewhere?

Adrian Popa said...

I haven't been following comments on this blog, mainly because I never knew people were adding comments :)

The reason I wrote that article is that I was faced with the same problem, having to troubleshoot somebody 200km away, and once I knew how to solve it I shared it with avid google searchers :)

I'm glad you found it useful!

Eugene Goldman said...

This is also good.
Works well, doesn't require installation or specific config, works behind gateways NAT as well as within one LAN.