2

I launch an AutoHotkey script (.ahk) when Windows 10 boots, but it takes 10-20 seconds from when I'm logged in until the script starts. The strange thing is that the overall system is very snappy, so I can search and launch applications manually as soon as I'm logged in. Manually searching for and launching Chrome for instance, takes less than a second.

So the problem doesn't seem to be a hardware bottleneck; it looks like a software delay in Windows 10. Could it be that one of the other startup applications takes a long time to launch? "NVIDIA Backend" is one of the other two applications that launch on startup, could that be causing this strange delay? I used to run Windows 7 until a month back, and never once saw this issue.

Edit: all my startup applications are delayed for some seconds when I start Windows, which is frustrating as I always launch my different development tools via AutoHotkey. Is there any way to raise priority, or have them start earlier in the Windows boot. Does for instance HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run execute before the Startup folder? Any suggestion is welcome!

Improve this question
4
  • Have you tried switching things off at startup, temporarily, to see if that helps? Some things need to login online, like Microsoft OneDrive, and this can take some time. Perhaps these things are being prioritised over your AHK script.
    – Dave
    Commented Jul 20, 2016 at 19:01
  • It likely is your other programs that are configured to start, when the profile is accessed, that is causing the delay. You ask if an application could be at fault, but you are the only one who can verify, if the other application is indeed the culprit.
    – Ramhound
    Commented Jul 20, 2016 at 19:02
  • maybe windows defender scans the script and casues the delay. try to temporarily disable the real time protection
    – magicandre1981
    Commented Jul 21, 2016 at 4:57
  • Your suggestions may well be true. Is there any way to check what is causing the delay? Do applications at startup launch one after the other, or are they started "fire and release?"
    – Jonas Byström
    Commented Jul 21, 2016 at 19:42

1 Answer 1

Reset to default
5
+50

The startup delay can be modified in the registry as follows :

  • Enter regedit
  • Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Serialize
  • If Serialize does not exist, right-click on Explorer, choose New -> Key, and enter its name as Serialize
  • Click on Serialize
  • In the right-hand pane, right-click on empty space, choose New -> DWORD (32-bit) value, enter its name as StartupDelayInMSec and set it to 0.
  • Reboot.

Other hints which might help :

  • Disable Fast Boot

  • Adjust Virtual Memory Settings
    Type Performance into the Start Menu and choose the Adjust the appearance and performance of Windows. Under the Advanced tab, you’ll see the size of the paging file (another name for virtual memory). Click Change to edit it. At the bottom of the screen you’ll see a Recommended amount of memory and a Currently Allocated amount. Ensure that current allocation is not way over the recommended number.

  • Turn off Bash for Windows if you have installed it and don't need it.

  • Update graphics drivers from the manufacturer's support website.

Improve this answer
1
  • The serialize registry thing did the trick, it now starts in a couple of seconds.
    – Jonas Byström
    Commented Feb 2, 2018 at 8:51

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .