Skip to main content

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!
Labels:

Comments

mikespicer.net 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!!!

-mikespicer.net
January 1, 2012 at 7:27 AM
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?
January 9, 2012 at 6:50 PM
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!
November 15, 2012 at 1:19 PM
Post a Comment

Popular posts from this blog

Home Assistant + Android TV = fun

Here's a quick setup guide for controlling your Android TV from within Home Assistant. I've used it to control a genuine Android TV (Philips 7304) and an Odroid N2 running Android TV. For this to work you need ADB access. It can usually be enabled from within Developer Settings. The great part is - you don't need root access! The most important things are described in the androidtv component for Home Assistant: https://www.home-assistant.io/integrations/androidtv/ Make sure you go through the adb setup. My configuration is simple (inside configuration.yaml): media_player:   - platform: androidtv     name: TV Bedroom ATV     host: 192.168.1.61     device_class: androidtv Once Home Assistant restarts, your TV might require you to accept the connection (adb authentication). This happens only once (or until you reset your ATV to factory settings). Once running the integration will show you the current ATV state (on or off) and al...
6 comments
Read more

SmokePing + InfluxDB export + docker + slaves + Grafana = fun

I've been working for a while on this project - with the purpose of getting SmokePing measurements from different hosts (slaves) into InfluxDB so that we can better graph them with Grafana. The slaves run multiple Smokeping instances inside Docker so that they have separate networking (measure through different uplinks, independently). This will not be a comprehensive configuration guide, but a quick "how to" to handle setup and basic troubleshooting. It assumes you already know how to set up and operate a regular Smokeping install with or without slaves and that you are fluent in Smokeping configuration syntax, know your way around Docker and aren't a stranger from InfluxDB and Grafana (sorry, there's a lot of information to take in). 1. Getting Smokeping with InfluxDB support - you can get it either from the official page (most changes have been merged) - https://github.com/oetiker/SmokePing (PR discussion here: https://github.com/oetiker/SmokePing/issues/...
16 comments
Read more

Android: Adding scp/sftp support to dropbear and mounting with sshfs

I have recently received an android smartphone, and one of the first things I did with it was to root it :). This allows power-usres to get the most out of their hardware. The next thing on my list was to set up a SSH server and to be able to transfer files between my Linux system and my phone (by the way, I'm running Android 4.1 and it seems USB mass storage support has been removed. MTP/PTP modes have either horrible transfer speed or are poorly supported in Ubuntu). With the above in mind, the plan was to: Enable tethering on the phone Run a SSH server to support issuing remote commands and file transfer (FTP might have been an alternative, but I'm a SSH adept). Browsing the market I found  SSHDroid which does all that it advertised. Problem is - the free version conflicts with my add-blocking apps and requests that they are disabled to run. For me, this is a big nuisance, so I kept looking. I found Dropbear SSH Server 2 , which is completely free, but doesn'...
5 comments
Read more