Recommended Posts

Hello folks,

At work, we have an area where computers are available to the public. Because of this, we had them locked down fairly well with a combination of group policies, regedits, filters, etc. Previously, these machines were running XP, and we had them set up to automatically logon to a local standard user profile. If we needed to do some maintenance on these pcs, we would bypass the autologon by holding down the shift key while Windows was loading. We've just replaced the machines, and I want to use Windows 7 on them now. However, the shift-to-bypass-autologon functionality has been removed in Windows 7, and I have yet to find it's replacement or alternative. The autologon function still exists, but you can no longer bypass it by holding shift.

So, if you edit the registry to force an automatic logon to a standard user account, you're stuck there and can't get onto a different account. Does anyone know how to get out of this situation under Windows 7?

Thanks!

Link to comment
https://www.neowin.net/forum/topic/1054460-bypassing-autologon-in-windows-7/
Share on other sites

Apparently (and I don't know this for certain due to not having a copy of Windows 7 handy to test it) you're supposed to alternate between tapping the left shift key and the right shift key. It's something to do with timing, using the shift key works but only if pressed at a specific time.

Let me know if that works though, it might be a load of rubbish.

I think it was the registry edit instead of using the "controlpasswords2" method that Microsoft recommends.

Same person had your issue and MS's recommendation was to go back and use the proper method.

http://answers.microsoft.com/en-us/windows/forum/windows_7-security/windows-7-autologin-bypass-disabled/04e50d02-d3e9-41d7-ab2d-c311ce93a715

Log off and then back in to the account you want.

Wow, great reeeding skillz, brite won! Don't reply if you haven't a freaking clue...

I've had no problems with the holding the left shift key on Windows 7 to bring up the login screen. :s We do a similar thing with some of our Windows 7 machines.

Seriously? It has never worked for me. BUT, i did find that Intrinsica's suggestion worked sometimes. On roughly 60% of the tries, I was able to reach a login screen. Works for me!

@the OP, by now, you should have read this: from http://en.wikipedia.org/wiki/List_of_features_removed_in_Windows_Vista : "It is not possible to override Autologon by pressing the SHIFT key before logon. The IgnoreShiftOverride registry value is ignored". It's one of the many features broken and which MS calls "by design" to avoid fixing it because it doesn't matter to Joe Average. :p

@the OP, by now, you should have read this: from http://en.wikipedia....n_Windows_Vista : "It is not possible to override Autologon by pressing the SHIFT key before logon. The IgnoreShiftOverride registry value is ignored". It's one of the many features broken and which MS calls "by design" to avoid fixing it because it doesn't matter to Joe Average. :p

I did read that, but it's not 100% true. Rapidly tapping both shift keys DOES bypass autologon, so this Average Joe is satisfied. :p

Edit: As stated elsewhere, I seriously doubt that it's the rapid tapping of both shift keys that actually does the trick. It's much more likely that you just have to hit a shift key at the exact right time to catch it. And tapping them both quickly just gets the job done. (Y)

I can't get those acrobatics (rapidly tapping two Shift keys) to work on my Windows 7 machines. It always auto-logs on. Btw I wasn't calling you Joe Average. :) Joe Averages are the one who think Windows 7 is perfect when really there are many such small and big things broken.

Guys dont hurt your self :) Take Logonexpert tool, it works like a charm and can interrupt autologon by shift

LogonExpert is not free. :) Would you mind giving us a license each? Paying $25 per computer for a feature that existed for ages in XP seems a bit too much. :)

What I do in this case is turn on Remote Desktop on the Windows 7 Computer. Then using an iPad or another network connected computer I establish a Remote Session with an administrator account. It will give me the choice to logout the currently logged in user. After I do the logout I can then walk over to the computer and work on it.

If the computer is not network connected because it is a self-contained kiosk then I bring a crossover cable with me, plug it directly to my laptop and establish a small network with between the two computers. It works even if you are using APIPA IP Addresses.

This topic is now closed to further replies.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!