This is only for the Compress2TXT part of the script (the creation of the actual EXE files used for the processes). Run the script directly, by (double-) click, not via console.
I'm trying to run the script (Windows 7) and getting the infamous red lettering errors. My .NET Framework version is 4.7.2 (installed with an offline installer), so I don't think I can "update" it any further. Errors look like this : Spoiler Compressed 2 txt : r85decode _temp~ ... Cannot index into a null array. At line:29771 char:65 + "@; $r=([regex]::Matches($res,'([^:\s]{1,5})')).value;$pad=5-$r[ <<<< -1].length;if($pad){$r[-1]=$r[-1]+"~~~~~".Remove($pad)} + CategoryInfo : InvalidOperation: (-1:Int32) [], RuntimeException + FullyQualifiedErrorId : NullArray Cannot convert argument "1", with value: "", for "WriteAllBytes" to type "System.Byte[]": "Cannot convert value "" to type "System.Byte[]". Error: "Invalid cast from 'Sy stem.DBNull' to 'System.Byte[]'."" At line:29778 char:25 + [IO.File]::WriteAllBytes <<<< ($file,$xe.nodeTypedValue); expand -R $file -F:* .; del $file -force + CategoryInfo : NotSpecified: ) [], MethodException + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Can't open input file: _temp~. Remove-Item : Cannot find path 'F:\Conversion\_temp~' because it does not exist. At line:29778 char:82 + [IO.File]::WriteAllBytes($file,$xe.nodeTypedValue); expand -R $file -F:* .; del <<<< $file -force + CategoryInfo : ObjectNotFound: (F:\Conversion\_temp~:String) [Remove-Item], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand As workarounds I have already tried the following: - Shrinking the original, long, multilevel path I was using to just "F:\Conversion" : errors remained the same (as above) ; - Manually creating subfolder "F:\Conversion\_temp~" : errors just changed to the following - Spoiler Compressed 2 txt : r85decode _temp~ ... Cannot index into a null array. At line:29771 char:65 + "@; $r=([regex]::Matches($res,'([^:\s]{1,5})')).value;$pad=5-$r[ <<<< -1].length;if($pad){$r[-1]=$r[-1]+"~~~~~".Remove($pad)} + CategoryInfo : InvalidOperation: (-1:Int32) [], RuntimeException + FullyQualifiedErrorId : NullArray Cannot convert argument "1", with value: "", for "WriteAllBytes" to type "System.Byte[]": "Cannot convert value "" to type "System.Byte[]". Error: "Invalid cast from 'Sy stem.DBNull' to 'System.Byte[]'."" At line:29778 char:25 + [IO.File]::WriteAllBytes <<<< ($file,$xe.nodeTypedValue); expand -R $file -F:* .; del $file -force + CategoryInfo : NotSpecified: ) [], MethodException + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument Any hints ? I might try the GUI next ... UPDATE: I just tried to install Powershell 6.1.1 from GitHub ... which required one Universal C Runtime ... which couldn't be installed, seemingly because my Win 7 is not activated. Guess I have a bunch of underlying issues to solve in this system before being able to run this script.
I want to download the enterprise version of ltsc, which one of the available ISOs do I go for? I downloaded en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958 along with the EVAL version, did I get the right one? Do I install the enterprise ISO and can I delete the EVAL one?
@cheerfuldeo en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.svf needs 17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x64FRE_en-us.iso for conversion This is Windows 10 1809 September release. SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425.svf needs 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us.iso for conversion This is Windows 10 1809 October release.
So I need the second one you mentioned ( 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-us.iso ) to get the latest LTSC Enterprise version?
@kukubau Have you checked svf2iso.exe inside zip with hashes -> #1? svf2iso.zip hash -> SHA1: b25fc4747df98cd399560618581657bbc484de60
The usual. Heuristic false-positive due to AHK to EXE 'compile'. Nothing new and nothing to do about.
Thx @Sajjo for the unhelpful attempt to help. The post you're linking to recommends that anyone with 'red letters' error msgs do an 'update' to .NET Framework 4.0. My post - which you're replying to - states in bold characters that I already have .NET Framework version 4.7.2. Care to elaborate ? PS: I suppose you also DID read the 'UPDATE' portion at the bottom of my post, of course.