Your description says that it is supported for Windows 2003 Server. However when I execute SNMsynth.cmd

I receive an error message that says

ERROR: This script is only for using under windows 2000/XP/2003. Press any key to continue.

...

Sorry, my fault. In SNMsynth.cmd substitute line 21:

FOR /F "TOKENS=3" %%I IN ('VER') DO IF /I "%%I"=="2000" (SET WIN2K=YES) ELSE IF /I "%%I"=="XP" (SET WINXP=YES) ELSE IF /I "%%I"=="2003" (SET WIN2K3=YES) ELSE ECHO ERROR: This script is only for using under win 2K/XP/2K3.&PAUSE&EXIT

with this:

FOR /F "TOKENS=3,4" %%I IN ('VER') DO IF /I "%%I"=="2000" (SET WIN2K=YES) ELSE IF /I "%%I"=="XP" (SET WINXP=YES) ELSE IF /I "%%J"=="5.2.3790]" (SET WIN2K3=YES) ELSE ECHO ERROR: This script is only for using under win 2K/XP/2K3.&PAUSE&EXIT

I can't test it, but it should work.

Edited March 12, 200917 yr by strel

Updated!

The new version integrates the fixes you submitted, and other new features.

Now it gives freedom to install whatever updated framework version without being bothered by the update system, as it happens since KB951847 family update was realeased to add nothing new.

Now it actually support absolutely all updates up to date even restricted ones.

Now win 2K users can install 2.0 SP2 in his/her systems. Actually they could have done this with the previous version and 3.5 SP1 full redist, though it wasn't documented.

And about KB928416 problem, it seems it has been fixed by MS since KB951847 was released, at least I can't reproduce it again. So I didn't include the fix I have to that issue in this version. But I want you to confirm this point to include it if necessary.

Enjoy!

Edited March 13, 200917 yr by strel

Hello Strel,

I can't find _SNMsynth.ini in the new package. There is a _SNMsynth.cmd, do we use this instead?

This is because I messed things with the .zip file. It's been fixed now.

Redownload.

Edited March 13, 200917 yr by strel

AVG reports "potentially malicious HackTool.GOS" inside KB951847_FIX.mst" file (in the Binary.KB951847_FIX executable in the .mst file).

Is it a false positive ?

AVG reports "potentially malicious HackTool.GOS" inside KB951847_FIX.mst" file (in the Binary.KB951847_FIX executable in the .mst file).

EDIT:

IT WAS A FALSE POSITIVE!.

But Nowadays the .mst file doesn't include an .exe file embedded anymore.

Edited April 29, 200917 yr by strel

The file _SNMsynth.ini contains the following:

PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=

PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES

PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=

OUTPUT=
MERGE_FRAMEWORKS=
VERBOSITY=
COMPRESSION_RATIO=

After start SNMsynth.cmd I receive an error:

To previous version SNMsynth.cmd of such error does not occur.

What is the problem?

Thx gora.

I left a few posibilities uncovered in a conditional statement, it's fixed now.

I've reuploaded cause I forgot to change ECHO ON to ECHO OFF at the beggining of the file. Those 2 of you who downloaded can change it manually or redownload... or show everything the script executes going by.

Edited March 14, 200917 yr by strel

F***

It's not my day, wrong encoding. Sorry.

Please redownload.

Not important, but I reuploaded again to correct a cosmetic issue in the error message for the absence of 7za.exe

Thx ferk

IT IS A FALSE POSITIVE!

AV is failing identifying the 2 .vbs inside this file in the form of .exe files:

Dim blnRunning, colProcesses
blnRunning = True
Do Until Not blnRunning
		Set colProcesses = GetObject( "winmgmts:{impersonationLevel=impersonate}" ).ExecQuery( "Select * From Win32_Process Where Name = '" & "mscorsvw.exe" & "'" )
	WScript.Sleep 100
	If colProcesses.Count = 0 Then
		blnRunning = False
	End If
Loop
Set WshShell = CreateObject( "WScript.Shell" )
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d37.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d3e.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d44.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\State", "1", "REG_DWORD"
Set WshShell = Nothing

and

Set WshShell = CreateObject( "WScript.Shell" )
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\"
Set WshShell = Nothing

So don't worry.

It's the first one only, compiled by ExeScript (from Everstrike Software) and compressed with UPX that triggers the AVG alert (even if uncompressed with UPX), the second being in readable source form.

By the way, thank you very much for this much-needed .Net packager

Probably is caused by the loop in the script. Check post #141 again, I've included definitive results.

I'm getting error uninstalling 2.0 SP2 and 3.0 SP2 and probably 3.5 SP1, versions using KB951847_FIX.mst not finding the .msi package on some scenarios, is not a problem of the .mst file.

But I fixed it yet and there's a new update!

I recomend that if you installed from installers/add-ons built with 20090313 or 20090314 of the script, you use the 20090315 new version to build new installers keeping the previous; uninstall 2.0 SP2, 3.0 SP2, 3.5 SP1 in case you can do it without errors, and reinstall.

In case uninstall process can't find .msi file, you can:

- If you kept the previous installers, unzip them and when the popup appear asking you for the .msi file, feed it with the corresponding .msi you've just unzipped.

- If yoy didn't keep the installers try the same procedure of the last point with the new installers.

- If that fail search in C:\windows\installer\ for a file to feed the popup, search 2019 KB files for .NET 2.0 SP2 and 691 KB files for .NET 3.0 SP2.

Hope you don't need that. Ask me if you have any problem.

Edited March 15, 200917 yr by strel

Hi there!

For me there is still problem integrating .NET 1.1 hotfixes. They popup, like when I use hotfix.exe /? switch, but using version 20090111 everything is OK.