Installation 'hung' with Windows 10 64bit (for 3 minutes)

[dgm5555]

Installation appeared to hang for 2-3 minutes with the message "Target was appended to PSModulePath"

I was about to kill it when it restarted.

(Installing 64bit version of v3.3.14.0 on Windows10 beta)

Edited July 15, 2015 by dgm5555
extra info

[guinness]

Anti-virus maybe?

[Melba23]

dgm5555,

My Autoit installations also hang at that point - although not for that long - so it is not just you.

M23

[JohnOne]

Probably it has to find where powershell keeps it's module path string before it can add the appropriate AutoIt directory to it.

[dgm5555]

The SciTE4 installation also hangs for a minute at "Tell Windows to Update Environment". Given the rest of the installation (and almost every other installation I've tried) takes 15-20 seconds on my system, this seems to me a significant glitch.

 

[Melba23]

dgm5555,

 I have asked Jon to pop in - it is his installer.

M23

[Jon]

Hmm, that just updating the PSModulePath environment variable. That's been in the installer (beta) for about a year and I've not seen any other reports. It takes about 1-5 seconds on my install usually.

@Jos are you changing any env variables - what is happening in the scite installer at "Tell Windows to Update Environment"?  In the main installer I'm using a nsis addon like this:

${EnvVarUpdate} $0 "PSModulePath" "A" "HKLM" "$INSTDIR\AutoItX" ; Append

 

[Jon]

The 1-5 seconds is explained by this:

http://forums.winamp.com/showthread.php?t=299969 

Not sure why it's not timing out on the OP machine though. 

[Jon]

@dgm5555 could you run these three scripts and post the results please? 

Script1

Global Const $HWND_BROADCAST = 0xFFFF
Global Const $WM_SETTINGCHANGE = 0x001A

Global Const $SMTO_BLOCK = 0x0001
Global Const $SMTO_NORMAL = 0x0000
Global Const $SMTO_ABORTIFHUNG = 0x0002

$time = TimerInit()
MsgBox(4096, "", "Script1")
_WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 5000, $SMTO_NORMAL)
MsgBox(4096, "", "Script time: " & Round(TimerDiff($time) / 1000, 2))

Func _WinAPI_SendMessageTimeout($hWnd, $iMsg, $wParam = 0, $lParam = 0, $iTimeout = 1000, $iFlags = 0)
    Local $aRet = DllCall('user32.dll', 'lresult', 'SendMessageTimeoutW', 'hwnd', $hWnd, 'uint', $iMsg, 'wparam', $wParam, _
            'lparam', $lParam, 'uint', $iFlags, 'uint', $iTimeout, 'dword_ptr*', 0)
    If @error Then Return SetError(@error, @extended, -1)
    If Not $aRet[0] Then Return SetError(10, _WinAPI_GetLastError(), -1)

    Return $aRet[7]
EndFunc   ;==>_WinAPI_SendMessageTimeout

 

Script2

Global Const $HWND_BROADCAST = 0xFFFF
Global Const $WM_SETTINGCHANGE = 0x001A

Global Const $SMTO_BLOCK = 0x0001
Global Const $SMTO_NORMAL = 0x0000
Global Const $SMTO_ABORTIFHUNG = 0x0002

$time = TimerInit()
MsgBox(4096, "", "Script2")
_WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 5000, $SMTO_BLOCK+$SMTO_ABORTIFHUNG)
MsgBox(4096, "", "Script time: " & Round(TimerDiff($time) / 1000, 2))

Func _WinAPI_SendMessageTimeout($hWnd, $iMsg, $wParam = 0, $lParam = 0, $iTimeout = 1000, $iFlags = 0)
    Local $aRet = DllCall('user32.dll', 'lresult', 'SendMessageTimeoutW', 'hwnd', $hWnd, 'uint', $iMsg, 'wparam', $wParam, _
            'lparam', $lParam, 'uint', $iFlags, 'uint', $iTimeout, 'dword_ptr*', 0)
    If @error Then Return SetError(@error, @extended, -1)
    If Not $aRet[0] Then Return SetError(10, _WinAPI_GetLastError(), -1)

    Return $aRet[7]
EndFunc   ;==>_WinAPI_SendMessageTimeout

 

Script3

Global Const $HWND_BROADCAST = 0xFFFF
Global Const $WM_SETTINGCHANGE = 0x001A

Global Const $SMTO_BLOCK = 0x0001
Global Const $SMTO_NORMAL = 0x0000
Global Const $SMTO_ABORTIFHUNG = 0x0002

$time = TimerInit()
MsgBox(4096, "", "Script3")
_WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 250, $SMTO_NORMAL)
MsgBox(4096, "", "Script time: " & Round(TimerDiff($time) / 1000, 2))

Func _WinAPI_SendMessageTimeout($hWnd, $iMsg, $wParam = 0, $lParam = 0, $iTimeout = 1000, $iFlags = 0)
    Local $aRet = DllCall('user32.dll', 'lresult', 'SendMessageTimeoutW', 'hwnd', $hWnd, 'uint', $iMsg, 'wparam', $wParam, _
            'lparam', $lParam, 'uint', $iFlags, 'uint', $iTimeout, 'dword_ptr*', 0)
    If @error Then Return SetError(@error, @extended, -1)
    If Not $aRet[0] Then Return SetError(10, _WinAPI_GetLastError(), -1)

    Return $aRet[7]
EndFunc   ;==>_WinAPI_SendMessageTimeout

 

Edited July 16, 2015 by Jon

[Jos]

@Jos

 are you changing any env variables - what is happening in the scite installer at "Tell Windows to Update Environment"?  In the main installer I'm using a nsis addon like this:

Yes, I am creating/updating SCITE_USERHOME in the SciTE4AutoIt3 installer and do something like:

!include "winmessages.nsh"
  !define env_hkcu 'HKCU "Environment" "SCITE_USERHOME"'   
  -- set the $SCITE_USERHOMEDIR to the correct path
  DetailPrint 'Add SCITE_USERHOME to registry'
  WriteRegExpandStr ${env_hkcu} $SCITE_USERHOMEDIR
  ; make sure windows knows about the change
  DetailPrint 'Tell Windows to Update Enviroment'
  SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000

Believe I first tried the available NSIS option but was having issues with that... not sure what any more, but found this one somewhere.

Is that going to be an issue in Win10?

Jos

Edited July 16, 2015 by Jos

[UEZ]

Win10 has a built-in VS (Windows Defender - Antimalware Service Executable) which is causing probably this delay.

Edited July 16, 2015 by UEZ

[Jon]

Nah, it's todo with hung windows I think. Each window has 5 seconds to respond to the env change message. So if 10 windows don't respond then the delay is 50 seconds.

I'm assuming that when the OP runs those scripts that one of them will be quicker.  In the installer I'm changing the SendMessage line to this:

!include "WinMessages.NSH"
...
...
System::Call "user32::SendMessageTimeoutW(i ${HWND_BROADCAST}, i ${WM_WININICHANGE}, i 0, w 'Environment', i 3, i 1000, i 0)"

Which will be quicker anyway (1 second timeout rather than 5), but also uses SMTO_BLOCK and SMTO_ABORTIFHUNG parameters. 

I should change the EnvUpdate() AutoIt function as well to include the SMTO_ABORTIFHUNG flag.

Edited July 16, 2015 by Jon
Added NSIS Include

[Jos]

What is stopping us from even making the timeout shorter as we shouldn't care too much about notification for the environment update to running programs?

Jos

[Jon]

In your case, probably nothing. For paths I'm not so sure. In the AutoIt source it's set to 15 seconds...It's instant on most machines anway and with the SMTO_ABORTIFHUNG parameter it won't wait at all.

[dgm5555]

Sorry about the delay.

@Jon you script seems to be timing how long before I press OK for the msgbox. Was that your intention?

I modified the script a bit (including the missing reference too) to the following which repeats the loop changing variables and averages the time:

Let me know though if I busted it from your intended purpose?

expandcollapse popup

#include <WinAPI.au3>
Global Const $HWND_BROADCAST = 0xFFFF
Global Const $WM_SETTINGCHANGE = 0x001A

Global Const $SMTO_BLOCK = 0x0001
Global Const $SMTO_NORMAL = 0x0000
Global Const $SMTO_ABORTIFHUNG = 0x0002

$time1=0
$time2=0
$time3=0

for $i = 1 to 100
    $time = TimerInit()
    _WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 5000, $SMTO_NORMAL)
    $time1 = $time1 + TimerDiff($time)

    $time = TimerInit()
    _WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 5000, $SMTO_BLOCK+$SMTO_ABORTIFHUNG)
    $time2 = $time2 + TimerDiff($time)


    $time = TimerInit()
    _WinAPI_SendMessageTimeout($HWND_BROADCAST, $WM_SETTINGCHANGE, 0, "Environment", 250, $SMTO_NORMAL)
    $time3 = $time3 + TimerDiff($time)

Next

ConsoleWrite(@CRLF & "Script1" & @CRLF)
ConsoleWrite("Script time: " & Round($time1 / 1000/100, 2) & @CRLF)
ConsoleWrite(@CRLF & "Script2" & @CRLF)
ConsoleWrite("Script time: " & Round($time2 / 1000/100, 2) & @CRLF)
ConsoleWrite(@CRLF & "Script3" & @CRLF)
ConsoleWrite("Script time: " & Round($time3 / 1000/100, 2) & @CRLF)


Func _WinAPI_SendMessageTimeout($hWnd, $iMsg, $wParam = 0, $lParam = 0, $iTimeout = 1000, $iFlags = 0)
    Local $aRet = DllCall('user32.dll', 'lresult', 'SendMessageTimeoutW', 'hwnd', $hWnd, 'uint', $iMsg, 'wparam', $wParam, _
            'lparam', $lParam, 'uint', $iFlags, 'uint', $iTimeout, 'dword_ptr*', 0)
    If @error Then Return SetError(@error, @extended, -1)
    If Not $aRet[0] Then Return SetError(10, _WinAPI_GetLastError(), -1)

    Return $aRet[7]
EndFunc   ;==>_WinAPI_SendMessageTimeout

The entire SciTe console output was:

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /prod /ErrorStdOut /in "C:\Users\dgm55\OneDrive\Documents\Scripts\test1.au3" /UserParams    
+>08:49:57 Starting AutoIt3Wrapper v.15.503.1200.1 SciTE v.3.5.4.0   Keyboard:00000809  OS:WIN_81/  CPU:X64 OS:X64    Environment(Language:0809)
+>         SciTEDir => C:\Program Files (x86)\AutoIt3\SciTE   UserDir => C:\Users\dgm55\AppData\Local\AutoIt v3\SciTE\AutoIt3Wrapper   SCITE_USERHOME => C:\Users\dgm55\AppData\Local\AutoIt v3\SciTE 
>Running AU3Check (3.3.14.0)  from:C:\Program Files (x86)\AutoIt3  input:C:\Users\dgm55\OneDrive\Documents\Scripts\test1.au3
+>08:49:57 AU3Check ended.rc:0
>Running:(3.3.14.0):C:\Program Files (x86)\AutoIt3\autoit3_x64.exe "C:\Users\dgm55\OneDrive\Documents\Scripts\test1.au3"    
--> Press Ctrl+Alt+Break to Restart or Ctrl+Break to Stop

Script1
Script time: 0.13

Script2
Script time: 0.13

Script3
Script time: 0.12
+>08:50:35 AutoIt3.exe ended.rc:0
+>08:50:35 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 38.5

 

[Jon]

None of those hung. It may be a quirk of the SendMessage used in the install then. But I've replaced that for the next beta anyway so keep and eye out for that and see if it fixes.

[RaiNote]

I am using Windows 10 too  but no delay.°-° Maybe it would help those who have a hung there to use Compatibility Mode Win XP or Win 7. :3

-MAYBE-

[Jon]

@dgm5555 If you could try the latest installer (3.3.14.1) it uses a different method for updating the env - see if that helps.

[mLipok]

@Jon can you update it here: 

 

As I sse last update was at 12 July.

 

 

EDIT: but maybe this is actual version only updated date is incorrect ?

 

Edited July 31, 2015 by mLipok