Announcement

Collapse
No announcement yet.

Windows 10 / HS3 automatic start from a cold boot

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kitar
    replied
    Thanks for the input. I am on Win10 Home edition. Actually I do have a Win10 Pro key so I am going to see if I can upgrade that machine without a re-install.

    Leave a comment:


  • RoChess
    replied
    Originally posted by Kitar View Post
    I have had a persistent startup problem with HS3 and now HS4. The Task Scheduler starts HS4 program as expected but the Speaker.exe never executes unless I log in and manually run it. Even though the Start Speaker checkbox in HS Setup is ticked, it never runs.

    I'm on 20H2 as of a few days, and HomeSeer, SpeakerClient and Sentry load just fine on a single TaskScheduler task to load HS3.exe (no time yet to upgrade) at log-on of the primary Windows 10 user. I've also have it check for "Run whether user is logged on or not", however the primary task itself triggers at "At log on of HOMESEER\HomeSeer" (yes, I was super creative in naming WORKGROUP and User account).

    I've got one extra task added that runs shutdown.exe /l to then immediately log-off the user and keep things somewhat more secure.

    This works well if you can use the 'Netplwiz' method, but I have a feeling you are using "Windows 10 Home" and not the "Windows 10 Pro" that this tool is designed for which might be why you're seeing errors.

    For "Windows 10 Home", use WinKey+R (or right click on Windows 10 Start menu item and select "Run...") try "control userpasswords2" without the quotes and confirm any UAC notice you might get that you wish to allow access. Switch to the "Users" tab if needed.

    If the checkbox for "Users must enter a username and password to use this computer" is already checked then simply uncheck it and click "Apply" button, which will then ask you to enter password and you can verify that your username is listed in the box underneath checkbox. Otherwise re-enable checkbox, and use the "Add..." button to add your username, and then uncheck the checkbox again to ensure Windows will boot into desktop without requiring password.

    PS: HomeSeer > Tools > Setup > On the 'General' tab, the "Launch Speaker Client on Startup" entry is CHECKED, right? Also wise to have the "HSSentry (Software System Monitor)" option checked as well.

    PPS: Are you perhaps trying to boot into the system without a password on a Microsoft account? Far as I know a true local-user-account is needed, so be sure to create one and use that one to boot into the system. Never tried that on a Microsoft account, unless it was tied to a local-user account.

    Leave a comment:


  • RoChess
    replied
    Originally posted by aimless View Post
    ya know, i'm not sure if you are a smart *** or just smart.
    The truth often lies in the middle

    It is indeed risky to use /F because it can lead to corruption on open-file handles, such as for example database not closing properly. This can be compensated in SQLite for example with a PRAGMA check, but then it relies on HS4.exe to do that check before it starts. Backups are always a good idea, but that is regardless of you using such a script or not. The other option is to check for open-file handles with an advanced tool such as procexp.exe from SysInternals, which can also be batch-scripted via command-line.

    However, you ommitted a lot of details, because the key question obviously in your case is digging deep to find out why a normal shutdown process isn't working. Do the logs give you any insight? or it is just a matter of patience and that things take a little longer for you? Are there any errors preventing it? Have you looked into launching HomeSeer is a different way so that it shuts down easier?

    Still, power can fail, computers can abruptly halt processing for other reasons, so it is always wise to have the ability to survive such a shut-down, and I've got batch-scripts myself to /F(orce) the close down of applications remotely. For me it is when I RDP into a system via concurrent-RDP and need to shut down an application on the main session. Without /F I cannot do this, because I don't have visual or physical access to 'Okay' the normal shutdown process.

    Have you looked into BLShutdown plugin?

    Leave a comment:


  • ServiceXp
    replied
    Originally posted by aimless View Post

    Any ideas? I wrote the script and tested, got this back (using pause to debug):
    ________________________________________
    taskkill /IM HS4Sentry.exe
    pause
    taskkill /IM HS4.exe
    pause
    ________________________________________
    C:\Windows\system32>taskkill /IM HS4Sentry.exe
    ERROR: The process "HS4Sentry.exe" with PID 1816 could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    C:\Windows\system32>pause
    Press any key to continue . . .

    C:\Windows\system32>taskkill /IM HS4.exe
    ERROR: The process "HS4.exe" with PID 11500 could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    C:\Windows\system32>pause
    Press any key to continue . . .
    ________________________________________
    Are you testing via an actual windows shutdown event? Or testing in just the .cmd?

    I'm not sure why it doesn't work for HS4. I would NOT use the /F switch as that will almost guarantee corruption.

    I don't think there is any need to shut down the Sentry, So I would get rid of everything in except for taskkill /IM HS4.exe. (don't pauses) and try it in an actual shutdown or restart event.

    Leave a comment:


  • Kitar
    replied
    I have had a persistent startup problem with HS3 and now HS4. The Task Scheduler starts HS4 program as expected but the Speaker.exe never executes unless I log in and manually run it. Even though the Start Speaker checkbox in HS Setup is ticked, it never runs.

    I created a Startup Task with a one minute start delay, allowed it to stop any running copies, run if logged in not, highest permission, startup folder is set C:\HS4
    When I look at the Task Scheduler it shows that the speaker task is running.

    I have tried using the netplwiz but in the advanced settings it warns me that this version of Windows does not support that feature.


    HS4Pro 4.1.9.0
    Win10 Home
    C:\HS4 is the install folder

    Leave a comment:


  • aimless
    replied
    Originally posted by RoChess View Post

    The answer is pretty much in the response, just add /F to it, so use:

    taskkill /F /IM HS4Sentry.exe
    pause
    taskkill /F /IM HS4.exe
    pause
    ya know, i'm not sure if you are a smart *** or just smart. you have stated the obvious, but since you have almost 700 posts, i'm betting that happens a lot.

    it was the WISDOM of applying a force to the shutdown that I question, maybe i needed to spell it out for the keyboard warriors out there.

    Leave a comment:


  • RoChess
    replied
    Originally posted by aimless View Post
    Any ideas? I wrote the script and tested, got this back (using pause to debug):
    The answer is pretty much in the response, just add /F to it, so use:

    taskkill /F /IM HS4Sentry.exe
    pause
    taskkill /F /IM HS4.exe
    pause

    Leave a comment:


  • aimless
    replied
    Originally posted by ServiceXp View Post
    The Windows "restart" issue can easily be solve by shutting down HS3 using the following.

    It works in every type of shutdown I've tried.

    1) Create a new .txt file and add this: "taskkill /IM HS3.exe"
    2) Save and rename with extension .cmd
    3) Using: gpedit.msc Navigate to User Configuration >> Windows Settings >> Scripts | (Logon/Logoff)
    4) Double click on Logoff and add the path of the .cmd file you created.

    That's it. Windows will always logoff user(s) before restarting windows. and since HS3 will only start when a user logs on, problem solved.

    I still find @Rubber_Boot' s solution the best native Windows solution we have, as it's the only solution that I've found that allows .aspx pages to be served up correctly.

    NOTE: You will want to add this to Computer Configuration also.
    Any ideas? I wrote the script and tested, got this back (using pause to debug):
    ________________________________________
    taskkill /IM HS4Sentry.exe
    pause
    taskkill /IM HS4.exe
    pause
    ________________________________________
    C:\Windows\system32>taskkill /IM HS4Sentry.exe
    ERROR: The process "HS4Sentry.exe" with PID 1816 could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    C:\Windows\system32>pause
    Press any key to continue . . .

    C:\Windows\system32>taskkill /IM HS4.exe
    ERROR: The process "HS4.exe" with PID 11500 could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    C:\Windows\system32>pause
    Press any key to continue . . .
    ________________________________________

    Leave a comment:


  • davidfcmke
    replied
    Originally posted by Rubber_Boot View Post
    Maybe this video will help.

    I have been a customer of Homeseer for 4 years and I could not speak more highly of them. Their product is ultra-reliable and does not need to be connected to the internet to work. Since I wrote this posting Homeseer posted a video https://www.youtube.com/watch?v=n6mmLKPrmXU to help you start from a cold boot.
    Thanks for posting. It has been working for me except that it seems to prevent Chrome from opening when I actually login. I have to kill the task in task manager and manually restart to get chrome to open a browser. (Win7 pc). Does it work just as well on HS4? Thanks.

    Leave a comment:


  • prsmith777
    replied
    Just another +1 for startup delayer. Easy to use and works great and it's free.

    Leave a comment:


  • TeleFragger
    replied
    i just dropped a .bat file into the all users startup folder and it works.

    I too was trying many other options like a few run keys, task scheduler, etc..

    i do use autologon from MS

    Leave a comment:


  • Bigstevep
    replied
    Originally posted by 22v10 View Post

    Tried allot of other Tech...None worked as well, Pfft , This was the Easiest and Best solution for me Startup Delayer. After auto login of user it fires off the Speaker client, Then 60 Seconds later HS3.exe Works great and its FREE..
    Glad to here it works for you! I’ve been using it for over a year with no issues and no screwing around with regedit etc. Next thing to do is set up your PC to restart automatically from a AC power failure In the bios. This way if power is cut off and comes back on your PC will start up and when windows starts up so will HS3/HS4.

    Leave a comment:


  • 22v10
    replied
    Originally posted by Bigstevep View Post
    I just use Startup Delayer. It's a little free piece of software that works like Task Scheduler but allows you to delay the startup of applications in Windows and then it automatically will start the application, like HS3/4. It works great and I just set my start up to delay one minute once windows is starting up it allows a minute to remove the load all the other apps starting up first. Of course your PC will need to auto logon user name and password first then let it rip, a minute or so later you'll see Homeseer cranking up.
    Tried allot of other Tech...None worked as well, Pfft , This was the Easiest and Best solution for me Startup Delayer. After auto login of user it fires off the Speaker client, Then 60 Seconds later HS3.exe Works great and its FREE..

    Leave a comment:


  • RoChess
    replied
    Originally posted by skybolt View Post
    Did not know there were three folders, only know about the two mentioned above. You may be right about it starting too soon. I will look at that next time I look at this. Thanks.
    Things get interesting when you dig deep, and you probably have the following on your system (Except on N-version where XBox app isn't installed by default):

    Folder locations:
    • "%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup"
    • "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Startup"
    • "C:\Users\Default\AppData\Roaming\Microsoft\Windows\Star t Menu\Programs\Startup" (only gets executed under certain conditions, otherwise it acts as a template for when you create a new user profile)
    • "%LOCALAPPDATA%\Packages\Microsoft.XboxGamingOverlay_8we kyb3 d8bbwe\LocalCache\Roaming\Microsoft\Windows\Start Menu\Programs\Startup"
    Registry:
    • \HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion \Run
    • \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio n\Run
    • \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\C urrentVersion\Run
    SysInternals (now owned by Microsoft) has an awesome tool to give you quick insight into that @ https://docs.microsoft.com/en-us/sys...loads/autoruns

    Placing shortcut to HS3/HS4 in "%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup" is the most appropriate location if that is the user account that logs in automatic into Windows and you have UAC de-activated, but you then still need to adjust the shortcut to launch HS3/HS4 as an administrator. Also you might need to launch the Speaker client separate to avoid issues.

    I personally prefer the Task Scheduler method, but there are countless of other methods, but each will come with their own pro/cons and that all ties into the underlying reasons why HomeSeer needs those administrative permissions.

    Leave a comment:


  • skybolt
    replied
    Originally posted by RoChess View Post
    ... Windows 10 has 3+ locations for each user.

    Each folder comes with its own UAC/ACL permissions and is executed at different times. ...
    Did not know there were three folders, only know about the two mentioned above. You may be right about it starting too soon. I will look at that next time I look at this. Thanks.

    Leave a comment:

Working...
X