Ошибка autoit error line 25408

;ДАННЫЕ
#include <Excel.au3>
#Include <File.au3>
$Povtor = InputBox("Колличество цыклов","Введите колличество цыклов") ;Количество цыклов

;ЗАПУСК EXCEL
Local $oAppl = _Excel_Open()
$BookAvto=_Excel_BookOpenEX($oAppl, @ScriptDir & 'Exel.xlsm')

For $j = 1 To $Povtor
;==============================================================================
;Определение переменных из Excel
$BookAvto.Worksheets("Лист1").Range("A1").Select ;Выбираем ячейку
$BookAvto.ActiveSheet.Application.Run("Копировать") ;Копируем ячейку в буфер обмена
$Papka=ClipGet() ;Присваиваем значение перемнной из буфера
$BookAvto.Worksheets("Лист1").Range("A1").Select ;Выбираем ячейку
$BookAvto.ActiveSheet.Application.Run("Копировать") ;Копируем ячейку в буфер обмена
$Zamena=ClipGet() ;Присваиваем значение перемнной из буфера
MsgBox(0, 'Циклы - ПРОЦЕСС', 'Номер цыкла: '&$j&' из '&$Povtor&'', 1)

;==============================================================================
;ПОИСК И ЗАМЕНА В ФАЙЛАХ
_FindFiles_1('C:Песочница'&Papka&'', '*.*') ;Замена

;==============================================================================
;УДАЛЕНИЕ СТРОКИ EXEL
$BookAvto.ActiveSheet.Application.Run("Сместить") ;Сместить
Sleep(100)
Next

_Excel_Close($oAppl)

MsgBox(0, 'Циклы - КОНЕЦ', 'КОНЕЦ!' & @CR & 'Сделано цыклов: '&$Povtor&'')

;ФУНКЦИЯ ПОИСКА И ЗАМЕНЫ
Func _FindFiles_1($sRoot, $sFile)
    Local $FileList
    $FileList = _FileListToArray($sRoot, $sFile, 1)
    If Not @error Then
        For $i = 1 To $FileList[0]
            ConsoleWrite($sRoot & '' & $FileList[$i] & @CR)
            $Read = FileRead($sRoot & '' & $FileList[$i]) ;Считываем файл
            $Replace = StringRegExpReplace($Read, 'Что нужно заменить', $Zamena ) ;Делаем изменение
            FileDelete($sRoot & '' & $FileList[$i]) ;Удаляем файл
            FileWrite($sRoot & '' & $FileList[$i], $Replace) ;На его место записываем измененный файл
        Next
    EndIf
    $FileList = _FileListToArray($sRoot, '*', 2)
    If Not @error Then
        For $i = 1 To $FileList[0]
            _FindFiles_1($sRoot & '' & $FileList[$i], $sFile)
        Next
    EndIf
EndFunc

Func _Excel_BookOpenEX($oExcel, $sFilePath, $bReadOnly = Default, $bVisible = Default, $sPassword = Default, $sWritePassword = Default, $bUpdateLinks = Default)
    ; Error handler, automatic cleanup at end of function
    Local $oError = ObjEvent("AutoIt.Error", "__Excel_COMErrFunc")
    #forceref $oError
    If Not IsObj($oExcel) Or ObjName($oExcel, 1) <> "_Application" Then Return SetError(1, @error, 0)
    If Not FileExists($sFilePath) Then Return SetError(2, 0, 0)
    If $bReadOnly = Default Then $bReadOnly = False
    If $bVisible = Default Then $bVisible = True
    Local $oWorkbook = $oExcel.Workbooks.Open($sFilePath, $bUpdateLinks, $bReadOnly, Default, $sPassword, $sWritePassword)
    If @error Then Return SetError(3, @error, 0)
    Local $oWindow = $oExcel.Windows($oWorkbook.Name) ; <== Modified
    If IsObj($oWindow) Then $oWindow.Visible = $bVisible ; <== Modified
    ; If a read-write workbook was opened read-only then set @extended = 1
    If $bReadOnly = False And $oWorkbook.Readonly = True Then Return SetError(0, 1, $oWorkbook)
    Return $oWorkbook
EndFunc   ;==>_Excel_BookOpen

Some users have reported an AutoIt error on Microsoft’s support forum. When that issue arises, users see an AutoIt Error message pop up every time Windows starts up.

The specified file path within that error message can vary, but despite the file path, there are a couple of solutions that you can use to fix this problem.

What is AutoIt3 EXE?

AutoIt v3 is a scripting language developed for automating and mimicking keystrokes, mouse movement, and window/control manipulation.

Is AutoIt needed?

This is not a necessary operation for Windows and may be stopped if it is known to cause difficulties.

File corruption is a common cause of problems with Windows, including this one. This can happen anytime for unknown reasons, but the issues are minor and can be easily fixed by running scans with DISM and SFC.

If your computer has one or more autorun keys left behind by an application that is no longer available, you are likely to run into one of the most typical instances in which you would get this sort of error.

Another factor you should consider is the possibility that your Windows files have been compromised by a virus or other form of malicious software.

There are other causes, but these are the most common ones. Here are also the most common errors reported by our users regarding AutoIt:

• AutoIt Error Line 0 file C:/Users – Conceivably, the cause is a conflict between a program or service and one or more of Windows’s processes to boot up.
• AutoIt Error Line 0 – You may test whether or not this is the case by forcing Windows to boot with only the essential drivers and applications for the starting process.
• Allocating memory AutoIt error – Using File Explorer, delete all entries that include AutoIt.
• AutoIt Error opening the file – This can occur due to the residual autoruns.
• AutoIt Error ServiceGet – Delete any string values associated with AutoIt from the Registry Editor.
• Logonui.exe AutoIt error – Try using Startup Repair.
• AutoIt error line 865 – Delete any AutoIt scripts running when Windows starts.
• AutoIt error in Windows 7/10/11 – This issue is not specific to one OS iteration, but rather to all of them, or the latest ones. However, the solutions below are applicable to each iteration.

Without any further ado, let’s jump into the list of solutions to AutoIt errors in both Windows 10 and 11. Follow along!

How do I get rid of AutoIt error?

1. Run a malware scan

The AutoIt error is often caused by malware known as Veronica, so you should start with a malware scan.

We suggest you use Eset Internet Security because it has a very high detection rate and multiple security features to ensure you are protected on all fronts.

Eset is an award-winning antivirus with a powerful anti-malware engine. It protects your PC in real-time, at all times, without impacting its functionality. 

Other notable features of Eset Internet Security include:

• Banking and payment protection
• Parental controls
• Webcam protection
• Anti-phishing technology
• Multilayered protection
• Malware and ransomware protection

Eset lets you run a one-time full scan of your PC that will detect and remove any threats. It is online and completely free. It will help remove any threats and allow you to try the software.

Eset Internet Security

Remove malware and secure your whole digital experience with award-winning antivirus technology.

2. Edit the registry

The detailed solution below describes how to edit your Registry in order to resolve the AutoIt error on Windows PCs. 

1. Open the Run tool

First, open the Run tool by right-clicking the Start button and selecting that option from the menu.

2. Enter this command in the Open box: regedit > Click Ok to open Registry Editor.

Enter the following command in the Open box: regedit. Then click OK to open the Registry Editor.

3. Click File on the Registry Editor window and select Export option.

Click File on the Registry Editor window. Select the Export option.

4. Enter a file name for the registry backup and save it.

Enter a file name for the registry backup. Choose a location for the registry backup file. Press the Save button.

5. Open this registry key path using a special coomand.

Open registry key path with: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRun

6. Search for REG_SZ strings in the Run registry key.

Look for these REG_SZ strings in the Run registry key: AdobeFlash, Windows Update, Adobe Update, and Google Chrome. Right-click all those REG_SZ strings and select Delete to erase them.

7. Then open this key in the Registry Editor:

ComputerHKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRun

8. Repeat the 6th step

Repeat the 6th step for the LOCAL_MACHINE Run key you’ve just opened.

9. Close Registry Editor

Close the Registry Editor, and restart your PC to see if the issue persists.

After making these changes, the AutoIt error in Windows 11 should be gone.

Note: The REG_SZ strings specified above will include autoit3.exe, windowsupdate.lnk, googleupdate.a3x, or googleupdate.lnk within their data paths. Entering those data path keywords within Registry Editor’s Find tool should also locate the REG_SZ strings you need to erase.

3. Uninstall AutoIt

1. Open the Run window. Type this Programs and Features command into Run: appwiz.cpl
2. Next, select the AutoIt program listed.
   
3. Click the Uninstall option for AutoIt.
4. Restart your desktop or laptop after uninstalling AutoIt.

You can uninstall AutoIt and more thoroughly erase its leftover files and registry entries with third-party uninstaller software. 

4. Remove AutoIt scripts from startup

1. Download Autoruns by pressing the Download Autoruns and Autorunsc option from Microsoft’s page.
2. Extract it, locate its executable file and run it as administrator.
3. Now input autoit3 in the Filter box.
   
4. Locate AutoIt, right-click it, and choose Delete.

You can remove AutoIt scripts from the Windows startup with Autoruns. That’s one of the most detailed startup monitor tools for Windows. Using this tool, you should be able to fix the AutoIt error line 0 error opening the file message.

5. Reset your Windows 10

1. Open the Settings app by pressing Windows + I and navigate to the Update & Security section.
   
2. Select Recovery from the left pane. In the right pane, click on Get started button in the Reset this PC section.
   
3. Choose the option to keep your files and follow the instructions on the screen.
4. Once the process is finished, you’ll have a fresh installation of Windows ready.

Remember that factory reset removes installed applications, so you’ll have to install them again.

Is AutoIt V3 script a virus?

If you have used AutoIt for any significant amount of time, you are probably aware that it is an excellent and highly effective scripting language.

As is the case with all vital languages, one of the potential drawbacks is the generation of viruses by individuals with nefarious intentions.

Your installation of AutoIt does not include any viruses, and if a script you have written is flagged as a virus even though you do not intend to cause harm, it is an example of a false positive.

Is AutoIt malicious?

No, unless you haven’t downloaded the software from the official source, AutoIt is completely safe.

For more automation software, check out our article with the five best automated macro software.

Did you find a solution to this problem on your own? Feel free to share it with us in the comments section below.

Some users have reported an AutoIt error on Microsoft’s support forum. When that issue arises, users see an AutoIt Error message pop up every time Windows starts up.

The specified file path within that error message can vary, but despite the file path, there are a couple of solutions that you can use to fix this problem.

What is AutoIt3 EXE?

AutoIt v3 is a scripting language developed for automating and mimicking keystrokes, mouse movement, and window/control manipulation.

Is AutoIt needed?

This is not a necessary operation for Windows and may be stopped if it is known to cause difficulties.

File corruption is a common cause of problems with Windows, including this one. This can happen anytime for unknown reasons, but the issues are minor and can be easily fixed by running scans with DISM and SFC.

If your computer has one or more autorun keys left behind by an application that is no longer available, you are likely to run into one of the most typical instances in which you would get this sort of error.

Another factor you should consider is the possibility that your Windows files have been compromised by a virus or other form of malicious software.

There are other causes, but these are the most common ones. Here are also the most common errors reported by our users regarding AutoIt:

• AutoIt Error Line 0 file C:/Users – Conceivably, the cause is a conflict between a program or service and one or more of Windows’s processes to boot up.
• AutoIt Error Line 0 – You may test whether or not this is the case by forcing Windows to boot with only the essential drivers and applications for the starting process.
• Allocating memory AutoIt error – Using File Explorer, delete all entries that include AutoIt.
• AutoIt Error opening the file – This can occur due to the residual autoruns.
• AutoIt Error ServiceGet – Delete any string values associated with AutoIt from the Registry Editor.
• Logonui.exe AutoIt error – Try using Startup Repair.
• AutoIt error line 865 – Delete any AutoIt scripts running when Windows starts.
• AutoIt error in Windows 7/10/11 – This issue is not specific to one OS iteration, but rather to all of them, or the latest ones. However, the solutions below are applicable to each iteration.

Without any further ado, let’s jump into the list of solutions to AutoIt errors in both Windows 10 and 11. Follow along!

How do I get rid of AutoIt error?

1. Run a malware scan

The AutoIt error is often caused by malware known as Veronica, so you should start with a malware scan.

We suggest you use Eset Internet Security because it has a very high detection rate and multiple security features to ensure you are protected on all fronts.

Eset is an award-winning antivirus with a powerful anti-malware engine. It protects your PC in real-time, at all times, without impacting its functionality. 

Other notable features of Eset Internet Security include:

• Banking and payment protection
• Parental controls
• Webcam protection
• Anti-phishing technology
• Multilayered protection
• Malware and ransomware protection

Eset lets you run a one-time full scan of your PC that will detect and remove any threats. It is online and completely free. It will help remove any threats and allow you to try the software.

Eset Internet Security

Remove malware and secure your whole digital experience with award-winning antivirus technology.

2. Edit the registry

The detailed solution below describes how to edit your Registry in order to resolve the AutoIt error on Windows PCs. 

1. Open the Run tool

First, open the Run tool by right-clicking the Start button and selecting that option from the menu.

2. Enter this command in the Open box: regedit > Click Ok to open Registry Editor.

Enter the following command in the Open box: regedit. Then click OK to open the Registry Editor.

3. Click File on the Registry Editor window and select Export option.

Click File on the Registry Editor window. Select the Export option.

4. Enter a file name for the registry backup and save it.

Enter a file name for the registry backup. Choose a location for the registry backup file. Press the Save button.

5. Open this registry key path using a special coomand.

Open registry key path with: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRun

6. Search for REG_SZ strings in the Run registry key.

Look for these REG_SZ strings in the Run registry key: AdobeFlash, Windows Update, Adobe Update, and Google Chrome. Right-click all those REG_SZ strings and select Delete to erase them.

7. Then open this key in the Registry Editor:

ComputerHKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRun

8. Repeat the 6th step

Repeat the 6th step for the LOCAL_MACHINE Run key you’ve just opened.

9. Close Registry Editor

Close the Registry Editor, and restart your PC to see if the issue persists.

After making these changes, the AutoIt error in Windows 11 should be gone.

Note: The REG_SZ strings specified above will include autoit3.exe, windowsupdate.lnk, googleupdate.a3x, or googleupdate.lnk within their data paths. Entering those data path keywords within Registry Editor’s Find tool should also locate the REG_SZ strings you need to erase.

3. Uninstall AutoIt

1. Open the Run window. Type this Programs and Features command into Run: appwiz.cpl
2. Next, select the AutoIt program listed.
   
3. Click the Uninstall option for AutoIt.
4. Restart your desktop or laptop after uninstalling AutoIt.

You can uninstall AutoIt and more thoroughly erase its leftover files and registry entries with third-party uninstaller software. 

4. Remove AutoIt scripts from startup

1. Download Autoruns by pressing the Download Autoruns and Autorunsc option from Microsoft’s page.
2. Extract it, locate its executable file and run it as administrator.
3. Now input autoit3 in the Filter box.
   
4. Locate AutoIt, right-click it, and choose Delete.

You can remove AutoIt scripts from the Windows startup with Autoruns. That’s one of the most detailed startup monitor tools for Windows. Using this tool, you should be able to fix the AutoIt error line 0 error opening the file message.

5. Reset your Windows 10

1. Open the Settings app by pressing Windows + I and navigate to the Update & Security section.
   
2. Select Recovery from the left pane. In the right pane, click on Get started button in the Reset this PC section.
   
3. Choose the option to keep your files and follow the instructions on the screen.
4. Once the process is finished, you’ll have a fresh installation of Windows ready.

Remember that factory reset removes installed applications, so you’ll have to install them again.

Is AutoIt V3 script a virus?

If you have used AutoIt for any significant amount of time, you are probably aware that it is an excellent and highly effective scripting language.

As is the case with all vital languages, one of the potential drawbacks is the generation of viruses by individuals with nefarious intentions.

Your installation of AutoIt does not include any viruses, and if a script you have written is flagged as a virus even though you do not intend to cause harm, it is an example of a false positive.

Is AutoIt malicious?

No, unless you haven’t downloaded the software from the official source, AutoIt is completely safe.

For more automation software, check out our article with the five best automated macro software.

Did you find a solution to this problem on your own? Feel free to share it with us in the comments section below.

Thanks for the tip. However, in order for them to use my application, this *must* complete successfully.

Rather than detecting whether it is an object or not and then moving on in the script with or without the information, I’m looking for the root cause of the error and would hopefully be able to tell my user «you need to turn X service back on or install Y software in order to make it work.»

Any ideas on this?

I came across this error as well, while converting some code from an example and trying to run the script in a function and then try to use the same obj code in another function — it did not work. I had rewrite it so it did not use it, but it worked fine in the first function call. Maybe you are having the same problem. Take a look at this code.

; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.1 beta
; Author:        Thorsten Meger <Thorsten.Meger@gmx.de>  & ...
;
; Script Function:
;   Windows XP Information displayed in a GUI
;   with Office-Key (only Office XP or 2003 supported)
;
; UPdated by nitekram on 032106 - OnEvent
;
; ----------------------------------------------------------------------------
;

#include-once
;Global variables
Global $product = ""; Office product Version (XP or 2003)
Global $counter = 3; Counter for progressBar
Global $wait = 150; Wait for progessBar

Global $description_I, $windowsType_I, $serialNumber_I, $ProductKey_I, $InstallDate_I, $LastBootUpTime_I, $RegisteredOwner_I, $officeKey_I, $officeKey_L

Global $objOperatingSystem, $colSettings, $Close

Global $Description_B, $status_L, $Bin, $key4RegisteredOwner, $GUI, $counter, $progressbar

Global $wait, $objWMIService
Global $exit_B, $WindowsType_B, $SerialNumber_B, $ProductKey_B, $InstallDate_B, $LastBootUpTime_B, $registeredOwner_B, $OfficeKey_B

$objWMIService = ObjGet("winmgmts:{impersonationLevel=impersonate}!\.rootcimv2")
$colSettings = $objWMIService.ExecQuery ("Select * from Win32_OperatingSystem")



Func system()
    
;GUI
    $GUI = GUICreate("Windows Information", 685, 450, 250, 0)  ; 685, 450, 158, 127
    
;Labels
    $windowsInformation_L = GUICtrlCreateLabel("Windows Information", 8, 8, 659, 25)
    $status_L = GUICtrlCreateLabel("Information read out ...", 24, 80, 400, 17)
    $description_L = GUICtrlCreateLabel("Description", 16, 112, 103, 17)
    $windowsType_L = GUICtrlCreateLabel("WindowsType", 16, 152, 103, 17)
    $serialNumber_L = GUICtrlCreateLabel("SerialNumber", 16, 192, 103, 17)
    $ProductKey_L = GUICtrlCreateLabel("ProductKey", 16, 232, 103, 17)
    $InstallDate_L = GUICtrlCreateLabel("InstallDate", 16, 272, 103, 17)
    $LastBootUpTime_L = GUICtrlCreateLabel("LastBootUpTime", 16, 312, 103, 17)
    $RegisteredOwner_L = GUICtrlCreateLabel("RegisteredOwner", 16, 352, 103, 17)
    $officeKey_L = GUICtrlCreateLabel("OfficeKey", 16, 392, 103, 17)
    
;Input
    $description_I = GUICtrlCreateInput("Description", 130, 112, 389, 21)
    $windowsType_I = GUICtrlCreateInput("WindowsType", 130, 152, 389, 21)
    $serialNumber_I = GUICtrlCreateInput("SerialNumber", 130, 192, 389, 21)
    $ProductKey_I = GUICtrlCreateInput("ProductKey", 130, 232, 389, 21)
    $InstallDate_I = GUICtrlCreateInput("InstallDate", 130, 272, 389, 21)
    $LastBootUpTime_I = GUICtrlCreateInput("LastBootUpTime", 130, 312, 389, 21)
    $RegisteredOwner_I = GUICtrlCreateInput("RegisteredOwner", 130, 352, 389, 21)
    $officeKey_I = GUICtrlCreateInput("OfficeKey", 130, 392, 389, 21)
    
;Groups
    $informationPanel_G = GUICtrlCreateGroup("Information Panel", 8, 48, 585, 393)
    $status_G = GUICtrlCreateGroup("Status", 14, 64, 553, 41)
    $buttins_G = GUICtrlCreateGroup("Buttons", 608, 48, 65, 393)
    $office_G = GUICtrlCreateGroup("Microsoft Office", 14, 375, 553, 48)
    
    
;Buttons
    $exit_B = GUICtrlCreateButton("Exit", 616, 72, 49, 25, 0)
    GUICtrlSetOnEvent($exit_B, "CLOSEIT")
    $Description_B = GUICtrlCreateButton("clipboard", 616, 112, 49, 25, 0)
    GUICtrlSetOnEvent($Description_B, "CLOSEIT")
    $WindowsType_B = GUICtrlCreateButton("clipboard", 616, 152, 49, 25, 0)
    GUICtrlSetOnEvent($WindowsType_B, "CLOSEIT")
    $SerialNumber_B = GUICtrlCreateButton("clipboard", 616, 192, 49, 25, 0)
    GUICtrlSetOnEvent($SerialNumber_B, "CLOSEIT")
    $ProductKey_B = GUICtrlCreateButton("clipboard", 616, 232, 49, 25, 0)
    GUICtrlSetOnEvent($ProductKey_B, "CLOSEIT")
    $InstallDate_B = GUICtrlCreateButton("clipboard", 616, 272, 49, 25, 0)
    GUICtrlSetOnEvent($InstallDate_B, "CLOSEIT")
    $LastBootUpTime_B = GUICtrlCreateButton("clipboard", 616, 312, 49, 25, 0)
    GUICtrlSetOnEvent($LastBootUpTime_B, "CLOSEIT")
    $registeredOwner_B = GUICtrlCreateButton("clipboard", 616, 352, 49, 25, 0)
    GUICtrlSetOnEvent($registeredOwner_B, "CLOSEIT")
    $OfficeKey_B = GUICtrlCreateButton("clipboard", 616, 392, 49, 25, 0)
    GUICtrlSetOnEvent($OfficeKey_B, "CLOSEIT")
    
; SetFont
    $font = "Comic Sans MS"
    GUICtrlSetFont($windowsInformation_L, 16, 400, 4, $font)
    
;ProgressBar
    $progressbar = GUICtrlCreateProgress(140, 75, 400, 25)
    GUISetState(@SW_SHOW)
    
    $Close = GUISetOnEvent($GUI_EVENT_CLOSE, "CLOSEIT")
    
    createBAR()
    
EndFunc  ;==>system





Func createBAR()
    
    While $counter <> - 2
    ;$msg = GUIGetMsg()
        If $counter = 3 Then
            Sleep(500)
            GUICtrlSetData($status_L, "Initialize... " & $counter)
            progress()
            $counter -= 1
        ElseIf $counter = 2 Then
            GUICtrlSetData($status_L, "Initialize... " & $counter)
            progress()
            $counter -= 1
        ElseIf $counter = 1 Then
            GUICtrlSetData($status_L, "Initialize... " & $counter)
            progress()
            $counter -= 1
        ElseIf $counter = 0 Then
            GUICtrlSetData($status_L, "Ready ...")
            progress()
            $counter -= 1
        ElseIf $counter = -1 Then
            Dim $Bin = RegRead("HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion", "DigitalProductID")
            Dim $key4RegisteredOwner = "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion"
            
            
        ;; right here i took out
            #cs
                $objWMIService = ObjGet("winmgmts:{impersonationLevel=impersonate}!\.rootcimv2")
                $colSettings = $objWMIService.ExecQuery ("Select * from Win32_OperatingSystem")
            #ce
            For $objOperatingSystem In $colSettings
            Next
            GUICtrlSetData($description_I, StringMid($objOperatingSystem.Description, 1))
            GUICtrlSetData($windowsType_I, '(' & @OSVersion & ') ' & StringMid($objOperatingSystem.Caption, 19))
            GUICtrlSetData($serialNumber_I, StringMid($objOperatingSystem.SerialNumber, 1))
            GUICtrlSetData($ProductKey_I, DecodeProductKey($Bin))
            GUICtrlSetData($InstallDate_I, WMIDateStringToDate($objOperatingSystem.InstallDate))
            GUICtrlSetData($LastBootUpTime_I, WMIDateStringToDate($objOperatingSystem.LastBootUpTime))
            GUICtrlSetData($RegisteredOwner_I, RegRead($key4RegisteredOwner, "RegisteredOwner"))
            GUICtrlSetData($officeKey_I, getOfficeKey())
            GUICtrlSetData($officeKey_L, "Office " & $product)
            $counter -= 1
        EndIf
    WEnd
EndFunc  ;==>createBAR

Func CLOSEIT()
    
;tester()
    
    If @GUI_CtrlId = $exit_B Then
        exit_b()
    ElseIf @GUI_CtrlId = $Description_B Then
        ClipPut(GUICtrlRead($description_I))
    ;ClipPut(StringMid($objOperatingSystem.Description, 1)); did not work something about an obj variable
        GUICtrlSetData($status_L, "Description copied to clipboard")
    ElseIf @GUI_CtrlId = $WindowsType_B Then
        ClipPut(GUICtrlRead($windowsType_I))
;ClipPut('(' & @OSVersion & ') ' & StringMid($objOperatingSystem.Caption, 19))
        GUICtrlSetData($status_L, "WindowsType copied to clipboard")
    ElseIf @GUI_CtrlId = $SerialNumber_B Then
        ClipPut(GUICtrlRead($serialNumber_I))
;ClipPut(StringMid($objOperatingSystem.SerialNumber, 1))
        GUICtrlSetData($status_L, "SerialNumber copied to clipboard")
    ElseIf @GUI_CtrlId = $ProductKey_B Then
        ClipPut(GUICtrlRead($ProductKey_I))
;ClipPut(DecodeProductKey($Bin))
        GUICtrlSetData($status_L, "ProductKey copied to clipboard")
    ElseIf @GUI_CtrlId = $InstallDate_B Then
        ClipPut(GUICtrlRead($InstallDate_I))
;ClipPut(WMIDateStringToDate($objOperatingSystem.InstallDate))
        GUICtrlSetData($status_L, "InstallDate copied to clipboard")
    ElseIf @GUI_CtrlId = $LastBootUpTime_B Then
        ClipPut(GUICtrlRead($LastBootUpTime_I))
;ClipPut(WMIDateStringToDate($objOperatingSystem.LastBootUpTime))
        GUICtrlSetData($status_L, "LastBootUpTime copied to clipboard")
    ElseIf @GUI_CtrlId = $registeredOwner_B Then
        ClipPut(GUICtrlRead($RegisteredOwner_I))
    ;ClipPut(RegRead($key4RegisteredOwner, "RegisteredOwner"))
        GUICtrlSetData($status_L, "RegisteredOwner copied to clipboard")
    ElseIf @GUI_CtrlId = $OfficeKey_B Then
        ClipPut(GUICtrlRead($officeKey_I))
    ;ClipPut(getOfficeKey())
        GUICtrlSetData($status_L, "OfficeKey copied to clipboard")
    ElseIf $GUI_EVENT_CLOSE = -3 Then
        GUIDelete(@GUI_WinHandle)
    EndIf
    
EndFunc  ;==>CLOSEIT



Func exit_b()
    GUICtrlSetData($status_L, "Have a GREAT DAY!")
    Sleep(1500)
    GUIDelete(@GUI_WinHandle)
EndFunc  ;==>exit_b


; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.1 beta
; Author:        Unknown & Thorsten Meger <Thorsten.Meger@gmx.de>
;
; Script Function: Decode REG_BINARY
; ----------------------------------------------------------------------------

Func DecodeProductKey($BinaryDPID)
    Local $bKey[15]
    Local $sKey[29]
    Local $Digits[24]
    Local $Value = 0
    Local $hi = 0
    Local $n = 0
    Local $i = 0
    Local $dlen = 29
    Local $slen = 15
    Local $Result
    
    $Digits = StringSplit("BCDFGHJKMPQRTVWXY2346789", "")
    $BinaryDPID = StringMid($BinaryDPID, 105, 30)
    For $i = 1 To 29 Step 2
        $bKey[Int($i / 2) ] = Dec(StringMid($BinaryDPID, $i, 2))
    Next
    For $i = $dlen - 1 To 0 Step - 1
        If Mod(($i + 1), 6) = 0 Then
            $sKey[$i] = "-"
        Else
            $hi = 0
            For $n = $slen - 1 To 0 Step - 1
                $Value = BitOR(BitShift($hi, -8), $bKey[$n])
                $bKey[$n] = Int($Value / 24)
                $hi = Mod($Value, 24)
            Next
            $sKey[$i] = $Digits[$hi + 1]
        EndIf
    Next
    For $i = 0 To 28
        $Result = $Result & $sKey[$i]
    Next
    Return $Result
EndFunc  ;==>DecodeProductKey

; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.1 beta
; Author:        Unknown & Thorsten Meger <Thorsten.Meger@gmx.de>
;
; Script Function: WMIDateStringToDate (changed Date format)
; ----------------------------------------------------------------------------

Func WMIDateStringToDate($dtmDate)
    Return (StringMid($dtmDate, 7, 2) & "/" & _
            StringMid($dtmDate, 5, 2) & "/" & StringLeft($dtmDate, 4) _
             & " " & StringMid($dtmDate, 9, 2) & ":" & StringMid($dtmDate, 11, 2) & ":" & StringMid($dtmDate, 13, 2))
EndFunc  ;==>WMIDateStringToDate

; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.1 beta
; Author:        Thorsten Meger <Thorsten.Meger@gmx.de>
;
; Script Function: Display a "fake" progressbar at the beginning
; ----------------------------------------------------------------------------

Func progress()
    If $counter = 3 Then
        For $i = 0 To 20 Step 1
            GUICtrlSetData($progressbar, $i)
            Sleep($wait / 20)
        Next
    ElseIf $counter = 2 Then
        For $i = 20 To 50 Step 1
            GUICtrlSetData($progressbar, $i)
            Sleep($wait / 30)
        Next
    ElseIf $counter = 1 Then
        For $i = 50 To 80 Step 1
            GUICtrlSetData($progressbar, $i)
            Sleep($wait / 30)
        Next
    ElseIf $counter = 0 Then
        For $i = 80 To 100 Step 1
            GUICtrlSetData($progressbar, $i)
            Sleep($wait / 20)
        Next
        GUICtrlSetState($progressbar, $GUI_HIDE)
    EndIf
EndFunc  ;==>progress

; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.1 beta
; Author:        Thorsten Meger <Thorsten.Meger@gmx.de>
;
; Script Function:Get & decode OfficeKey
; ----------------------------------------------------------------------------

Func getOfficeKey()
    Local $List[1]
    Local $i = 1
    $var = RegRead("HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice11.0CommonInstallRoot", "Path")
    If $var <> "" Then
        $product = "2003"
        Dim $officeKey = "HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice11.0Registration"
    Else
        $var = RegRead("HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice10.0CommonInstallRoot", "Path")
        If @error <> 0 Then
            GUICtrlSetData($status_L, "Info: Unable to find installationPath, maybe no Office installed!")
            Return "No Office XP or 2003 found"
        EndIf
        If $var <> "" Then
            $product = "XP"
            Dim $officeKey = "HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice10.0Registration"
        EndIf
    EndIf
    Dim $var = RegEnumKey($officeKey, $i)
    If @error <> 0 Then
        GUICtrlSetData($status_L, "Info: Unable to find REG_BINARY 'DigitalProductID', maybe no Office installed!")
        Return "No Office XP or 2003 found"
    Else
        $List[$i - 1] = RegRead($officeKey & "" & $var, "DigitalProductID")
        If $List[$i - 1] = "" Then
            GUICtrlSetData($status_L, "Info: Unable to find REG_BINARY 'DigitalProductID', maybe no Office installed!")
        Else
            $key = $List[$i - 1]
            Return DecodeProductKey($key)
        EndIf
    EndIf
EndFunc  ;==>getOfficeKey

If you find out the answer let me know — I would like to be able to use in the future. Anyway if you take out the comments in the closeit() you will get the same type of error. I am not sure if it helps you but maybe your issue is the same and someone can look at this code.

;ClipPut(StringMid($objOperatingSystem.Description, 1)) ; did not work something about an obj variable