Followers 0

# Problems with Win8 8520?

## 9 posts in this topic

I was wondering if there are any developers out there who are having issues running AutoIT code on the latest revision of Win8?

I recently (about 4 months ago) wrote an auto-installer that pulled tools from a server and ran an auto install of each tool on systems.

This worked fine for revisions 8250, 8375 and 8400. However, when Win8 revision 8441 came around, I noticed some issues running some installers.

Now with the newest revision, 8520, it seems that FileCopy, DirCopy, ShellExecute, ShellExecuteWait, Run, and RunWait are all either locking up, or just failing to run.

The steps I take are:

Read from a cfg file the path of the installer, and any installer arguments

use ShellExecuteWait on installer with arguments

In the past, I've had no problems with this same exact code. UAC is off, #RequireAdmin is set, application is run as administrator, and even powershell is set to "Set-ExecutionPolicy UnRestricted"

Has anybody else had this problem? Anybody have workarounds?

##### Share on other sites

I completely agree, and this is why I haven't reported anything yet. Auto IT has been tremendously helpful to me as a Windows 8 developer, I had hoped there may be others who use Auto IT for this purpose.

If not, to at least be an early warning. Security is SUPER tight on Windows 8, which worries me quite a bit

##### Share on other sites

I completely agree, and this is why I haven't reported anything yet. Auto IT has been tremendously helpful to me as a Windows 8 developer, I had hoped there may be others who use Auto IT for this purpose.

If not, to at least be an early warning. Security is SUPER tight on Windows 8, which worries me quite a bit

Why would super tight security in an OS worry you?

Should make you feel fuzzy and safe.

Monkey's are, like, natures humans.

##### Share on other sites

Why would super tight security in an OS worry you?

Should make you feel fuzzy and safe.

lol. From a user standpoint, that's fine.

from a development standpoint, it's developer hell.

##### Share on other sites

Build 8441 is the latest version available for official download. I wouldn't advise using (potentially hacked) leaked builds for development. Thanks for bringing this up, I have built an app on 8400 and 8437, but sounds like I need to test 8441 to make sure it still works.

##### Share on other sites

Update: I tested my apps on 8441 x64 and had no problems. I hope that RTM doesn't have these problems that you mention.

I will note that my apps always run in Audit Mode, so it is possible that this problem may exist and I wouldn't run into it.

##### Share on other sites

Windows 8 build 8400 is the latest version that I can find on any Microsoft website, I only see an 8441 build on torrent sites, so I'm not sure how "official" that one is.

If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.
Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag Gude
How to ask questions the smart way!

I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from.

Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays.  -  ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script.  -  Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label.  -  _FileGetProperty - Retrieve the properties of a file  -  SciTE Toolbar - A toolbar demo for use with the SciTE editor  -  GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI.  -   Latin Square password generator

##### Share on other sites

#9 ·  Posted (edited)

Windows 8 build 8400 is the latest version that I can find on any Microsoft website, I only see an 8441 build on torrent sites, so I'm not sure how "official" that one is.

Builds up to 8441 are available to Microsoft Partners. Any newer builds are Microsoft internal for the most part.

Edited by Tripredacus

## Create an account

Register a new account

Followers 0

• ### Similar Content

I want to run a python script from autoit.
I know we can do this with shellexecute or run , but this python script takes 3 cmd line arguments.
How to pass them from autoit script?
I tried many ways.
Following solution also not working
e.g.
RunWait( 'fullpath\Python.exe Scriptpath\ReadLog.py  -f "file.log" -k "key" -e "errMsg" ') Found solution:
RunWait( 'fullpath\Python.exe ReadLog.py -f "file.log" -k "key" -e "errMsg" ', 'Working_directory_path')
PFB description:
https://stackoverflow.com/questions/45757834/how-to-pass-command-line-arguments-to-a-python-script-anyscript-while-executin

• By StMaSi
I'm attempting to code a Run or RunWait command that is a little on the long side and contains multiple sets of embedded quotes (as it would be issued from a CMD prompt), but can't for the life of me figure out the containing quotes as pertains to AutoIt. Here's the one-line command as it would be issued via a CMD prompt...
"\\AppServ\G$\Connectivity\Clients\Citrix\Receiver\14.5.0.10018\CitrixReceiver.exe" ADDLOCAL="ReceiverInside,ICA_Client,WebHelper,SSON,AM,SELFSERVICE,USB,DesktopViewer,Flash,Vd3d" ALLOWADDSTORE=A ALLOWSAVEPWD=A ENABLEPRELAUNCH=Y ENABLE_SSON=Yes STORE0="AppStore;https://receiver.domain.net/Citrix/Apps/discovery;on;AppStore" /EnableCEIP=false /includeSSON /noreboot /silent I've tried so many different combinations of surrounding quotes with Run and RunWait, I just don't understand why it's this difficult to get past this. Can anyone assist with this? Thank you. • By Simpel Hi. Local$sPDFtk = FileGetShortName(@ScriptDir & "\pdftk.exe") Local $sInputPDF = FileGetShortName(@ScriptDir & "\Prodis_Test.pdf") Local$sSig_1 = FileGetShortName(@ScriptDir & "\Sig_1.pdf") Local $sTempPDF = FileGetShortName(@ScriptDir & "\Prodis_Test_TEMP.pdf")$iSuccess = ShellExecuteWait($sPDFtk,$sInputPDF & " stamp " & $sSig_1 & " output " &$sTempPDF, "", "", @SW_HIDE) @ScriptDir is "H:\_Conrad lokal\Downloads\AutoIt3\_COX". As you can see there is a space in the path.
I know that ShellExecuteWait is working with FileGetShortName at the filename. It seems to me that I can't pass the parameters that way. But without FileGetShortName it's not working too.
• By WannaBeGut
Hello,
I just wrote a script that should copy data into my cloud using xcopy (cmd), but I want the Status Bar I have in my GUI to change it's text like that:
working. -> working.. -> working... -> working. ...
I would also like to make a button which interrupts xcopy (simply closing it should do the trick), but I don't know how to call ProcessClose("xcopy.exe") using a button, while I'am waiting for RunWait to finish.
Example:
$command = 'xcopy "' & @DesktopDir & '\text.txt"' & ' "\\ADMIN-CLOUD\private\" /EECHIY'$SW_STATE = @SW_HIDE RunWait(@ComSpec & " /c " & '"' & $command & '"', @DesktopDir,$SW_State) Please tell me if you need any further information!
• By ur
I have written a script to build the Installshield project file(.ism) to setup files(.msi or .exe based on the release settings..).
So when the user runs the script the process will be automatic for multiple ism files.
Func Build($sOutputIsm,$ReleaseName,$sFilePath="None",$NewName="None") ;build the ism to get the msi If not FileExists($sOutputIsm) Then Logging("File Not Found:$sOutputIsm$",4) MsgBox($MB_OK + $MB_ICONERROR, "Error", "Could not find file ""$sOutputIsm$"".") Return EndIf Logging("Started Building$sOutputIsm$",4) ShowTrayTip($AppName, "Started Building $sOutputIsm$", 10, $TIP_ICONASTERISK) Dim$sBuildExe,$sBuildCommand,$Ret $sBuildExe = FindFileInPath("ISCmdBld.exe", "%ProgramFiles(x86)%\InstallShield")$sBuildCommand = """$sBuildExe$"" -p ""$sOutputIsm$"" -r ""$ReleaseName$"" -s" ;MsgBox(0,"",$sBuildCommand)$Ret = RunWait($sBuildCommand) If$Ret <> 0 Then ShowTrayTip($AppName,"ISM Build Failed, Please build the ISM Manually.",10,$TIP_ICONHAND) MsgBox($MB_OK +$MB_ICONERROR, "Error", "Could not build ""$sOutputIsm$"". Please build manually.") Logging("Error $Ret$ while Building $sOutputIsm$",4) Return;Exit(1) Else ShowTrayTip($AppName,"ISM Build Completed",10,$TIP_ICONASTERISK) Logging("Completed Building $sOutputIsm$",4) if not StringCompare($NewName, "None")=0 then MoveEXE($sFilePath,$NewName) EndIf EndFunc The problem is when we run the ISCmdBuild.exe the RunWait will give whether fail or success but not what are the errors we got. If we use Run, it will give that logging but we don't have the feature of getting fail/success as RunWait. If we run the above code by removing -s and using redirection operator > to a file, it is running manually but failing with autoit. Like$sBuildCommand = """$sBuildExe$"" -p ""$sOutputIsm$"" -r ""$ReleaseName$"" > c:\logs\uday.log" Any help on this??

And also, in some machines the installshield shortcut is launching fine as licensed version but with ISCmdBld.exe it is giving error as licensing info missing or not registered.

Any suggestion on this too??