Search the Community

Hello!!! In the past I had problems adding an application as a default for an extension in Windows 10. (It was easy in windows 7 using Registry) But since Windows 8 It requires to do some steps more. I wrote a tool (in other programming language) months ago for handling it. But now I just want to share an AutoIt version. Check on GitHub. Saludos

Hello, I will put it as simple as possible Why this code runs perfectly on 32bit and it fails on 64bit? Local $hWND = WinGetProcess("[CLASS:LSS_app]") ConsoleWrite($hWND & @LF) Local $hModuleList = _WinAPI_EnumProcessModules($hWND) If @error Then ConsoleWrite("Error: " & @error & @LF) For $i = 0 To $hModuleList[0][0] - 1 ;~ If StringInStr($hModuleList[$i][1], "sysCap64.dll") Then ConsoleWrite($hModuleList[$i][0] & @LF) ;~ EndIf Next As the title says EnumProcessModules returns error 10 which I have no clue what it is. It must be something with autoit or my lack of coding because a similar code in C# will work like a charm on both x86 and x64 Process[] Processes = Process.GetProcessesByName("winLSS64Cap"); Process nProcess = Processes[0]; Handle = OpenProcess(0x10, true, (uint)nProcess.Id); for(int i = 0; i < nProcess.Modules.Count; i++) { Console.WriteLine(nProcess.Modules[i].ModuleName); }

I basically want to create a Windows 8 Training script for new users, so need a popup to show when they open the start menu. WinWait and WinWaitActive are never detecting on my Win8 64 bit computer when waiting for the new start screen window. I have used "Start menu" and "[CLASS:ImmersiveLauncher]" for the title, even "[CLASS:DirectUIHWND]" Below is the Window info the the Start Screen >>>> Window <<<< Title: Start menu Class: ImmersiveLauncher Position: 1920, 0 Size: 1920, 1080 Style: 0x96000000 ExStyle: 0x00200008 Handle: 0x0000000000010190 >>>> Control <<<< Class: DirectUIHWND Instance: 0 ClassnameNN: DirectUIHWND0 Name: Advanced (Class): [CLASS:DirectUIHWND; INSTANCE:0] ID: Text: Position: 0, 0 Size: 1920, 1080 ControlClick Coords: 138, 174 Style: 0x56000000 ExStyle: 0x00000000 Handle: 0x0000000000010192 >>>> Mouse <<<< Position: 2058, 174 Cursor ID: 0 Color: 0x180053 >>>> StatusBar <<<< >>>> ToolsBar <<<< >>>> Visible Text <<<< >>>> Hidden Text <<<< Explorer Browser Control I have this setup to run as a test when I press a hotkey: $title = WinGetTitle ("[ACTIVE]") $state = WinGetState ($title) ConsoleWrite ($title &" "& $state) I get "Start menu 0" its always 0 no matter what (it works correctly with other programs) I can get the PID of start menu but how can I then check when its active from that? Any help appreciated EDIT: I can only get the PID, Handle or anything else if the Start window is open. I cannot use win wait with any of this info though.

I want to switch from Windows 7 to Windows 8.1 ( x86 ) but I still want to code in AutoIt. Now I saw in the Description file that is only compatible upto Windows 7, but will it work also on 8 ? And yes Im referring to the latest Autoit version available !

The original resolution switcher by HTC works good on earlier Windows, but has two problems on Win8. When activated it creates a window telling the current resolution. It is given focus and thus forces Metro back to the desktop.It switches between the native 800x480 and 1024x600 which is to low to run Metro apps.To fix this I started with a simple script that switches to 1152x864 with a window that displays the resolution without grabbing focus.Later I added some extras: Option to skip the window altogetherSeparate resolution in desktop and MetroA simple installer/uninstaller for the HTC Shift (or other devices that use a synaptics touchpad in the same matter, check the code).Code moved to attachment. See next post for screenshots. ResSwitch source.rar The .au3 itselfModified (removed duplicate const's)Modified (removed duplicate const's and commented WinXP (+ earlier) code to reduce file size)ResSwitch.rar (previous downloads: 51)A compiled .exe (if you don't have AutoIt? lol).bat file calling the installer/uninstaller function (optional).ini file containing the standard settings (optional)

I need to to create and switch to a windows profile without user interaction which I got to work for the most part. I took care of creating a new account and I found a small trick online to switch a windows profile without user interaction(this needs to be done to create some registry which are changed later in the script). "Trick" artical found here. Basically, Kill the all exlorer.exe's then run a new explore.exe as the new user account I just made. This makes windows start setting up the profile and directories and it loads into the new enviorment. Works like a charm. But Windows 8 seems to get stuck doing this trick. I think explorer is not making the $WM_SETTINGCHANGE call to the einviorment it use to to change the settings. Trying this in windows 8 DOES cause windows to setup the new profile. You can see the "personalized settings" loading screen popup. But later I am left at a black screen with a taskbar and not much to work with. I tried starting exploer again with the task manager and it made the process but I was still at a black screen. I did some reasaerch was thinking doing a Dillcall to explorer with _WinAPI_SystemParametersInfo(, , , $SPIF_SENDCHANGE), but to be honest I have never done this b4 and its mostly shooting in the dark Any advice? I have made a small repoduction of the problem. Remeber the problem is on windows 8. #include <WinAPI.au3> ;create newuser account^ ;Login to new user account $Username = "johnsmith" $Password = "123pass" $Processarray = ProcessList() For $x = 1 To UBound($Processarray) - 1;search and distroy explorer.exe If StringInStr($Processarray[$x][0], "explorer.exe") > 0 Then $pid = $Processarray[$x][1] $handle = _WinAPI_OpenProcess(0x1, 0, $pid) DllCall("kernel32.dll", "int", "TerminateProcess", "int", $handle, "int", 1) EndIf Next RunAs($Username, @ComputerName, $Password, 1, "explorer.exe")

Hi all, i am struggeling with a problem creating a input box wich will automatic seperate the input letters with a - after 5 characters. example: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX i all ready have it limited to 29 characters and max of 29 characters. I hope any one can help me with this. The purpose for the script is, an automatic network installation of Windows 8. forum post.au3

I have some AutoIt scripts that run fine under Windows XP but do not run under Windows 8. The problem appears to be the _ExcelBookOpen statement fails. I've used the following example script from the Help file for a test. ; *************************************************************** ; Example 1 - Open an existing workbook and returns its object identifier. ; ***************************************************************** #include Local $sFilePath1 = @ScriptDir & "\Test.xls" ;This file should already exist Local $oExcel = _ExcelBookOpen($sFilePath1) If @error = 1 Then MsgBox(0, "Error!", "Unable to Create the Excel Object") Exit ElseIf @error = 2 Then MsgBox(0, "Error!", "File does not exist - Shame on you!") Exit EndIf Running this produces the Error message box Unable to Create the Excel Object. I'm using Microsoft Excel 2002. I need some help to correct or work around this problem. Thank you - Dick

I hate asking basic questions, however I have spent 2 days and hours reading the forums and trying everything I can think of and I am stuck. This whittled down simple winmove script works in XP and Win7 but does not work in desktop windows 8. Any hints? ;#RequireAdmin ;<-- makes no difference #AutoIt3Wrapper_run_debug_mode=Y ; use this to debug in console window <--- LOOK Opt("WinTitleMatchMode", -2) ;nocase partial match okay $pgm_title = "Run" Send("#r") ;open run box ;wait for it WinWait($pgm_title) ;partial match If Not WinActive($pgm_title) Then WinActivate($pgm_title) WinWaitActive($pgm_title) ;WinSetState($pgm_title, "", @SW_SHOW) ;make sure we can see it - makes no difference MsgBox(0,"Debug","Ready to move.") $hl = WinMove($pgm_title, "", 0, 0) ;WinSetState($pgm_title, "", @SW_ENABLE) ;enable it - makes no difference ;WinSetState($pgm_title, "", @SW_SHOW) ;make sure we can see it - makes no difference MsgBox(0,"Debug","Should be at 0,0 and handle = " & $hl & " 0=not found") $hl = WinMove($pgm_title, "", 100, 100, Default, Default, 100) ;move slowly keep current size ;WinSetState($pgm_title, "", @SW_ENABLE) ;enable it - makes no difference ;WinSetState($pgm_title, "", @SW_SHOW) ;make sure we can see it - makes no difference MsgBox(0,"Debug","Should be at 100,100 and handle = " & $hl & " 0=not found") MsgBox(0,"Debug","Move completed.") Send("{ESC}") ;be polite and close run box Exit #cs Works on XP Pro SP3 x32 (x86) Works on Win 7 Pro x32 (x86) Fails in Windows 8 Pro x64 desktop mode #RequireAdmin ;<-- makes no difference all versions seem to wait a time for the move but do NOT actually move the box #ce

Is anyone else experiencing this issue with Windows 8 Release Preview & Consumer Preview: I have several scripts that automate info filling info into windows. They, of course, rely on AutoIT recognizing the windows by REGEXPTITLE & REGEXPCLASS (usually both, unless the title is blank). The scripts work fine for hours after restarting but they all eventually fail to "see" the windows even though they are visible. I am specifically working with Maxthon 3 (the Download Manager Window) and NetSetMan Pro. My understanding is that Windows 8 does not run explorer persistently & that may be an issue. I really just wanted wanted to see if anyone else has experienced this problem with the 2 "official" Windows 8 releases. I know that the software is Beta, so don't flame my post with that old chestnut. EDIT: This is a multi computer problem

It doesn't seem that I can run Sysprep in Windows 8 RP x64 using @ComSpec. I have no problem running other apps using either Run() or RunWait() in the same app. I am testing in Audit Mode (Administrator account, UAC is disabled). I already searched the forums and didn't find any one else trying to execute Sysprep like this... This does not work when run compiled: Run ( @ComSpec & " /c c:\windows\system32\sysprep\sysprep.exe /oobe /shutdown") Returns error "is not recognized as an internal or external command, operable program or batch file." I don't know how to keep the ComSpec window open, so the only way for me to see this was to hold down the Enter key so I could see the error. Curiously, running this manually works fine: cmd.exe /c c:\windows\system32\sysprep\sysprep.exe /oobe /shutdown App is compiled for x86. OH! Do not try to run this on your workstation!!!