Microsoft Redistibutables
DesertJerry
31 Mar 2012
Just ran APUP.EXE and APUP2.EXE and downloaded the vcredist items. Started AutoPatcher in XP Pro w/SP3 - all items were in black. Investigated and determined that the error was fixed by changing:
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=>8
to
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
Had to do the same for version 2005 and 2010 - the truncated version appears to not work - the full version is required.
Did not check the x64 version yet but I expect the same result. Also, remember, AutoPatcher is a 32bit program, it cannot read the 64bit registry entries when run from wthin XP Pro x64
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=>8
to
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
Had to do the same for version 2005 and 2010 - the truncated version appears to not work - the full version is required.
Did not check the x64 version yet but I expect the same result. Also, remember, AutoPatcher is a 32bit program, it cannot read the 64bit registry entries when run from wthin XP Pro x64
ViroMan
31 Mar 2012
I got sidetracked again. Other things happened ... I am working on it again. Uninstalled all the old stuff and installed the new stuff. My firewall Agentum Outpost Pro needs it so when I uninstalled all the old stuff and rebooted the firewall failed to work. After installing the new stuff my firewall starts up so that is a good sign that the SP1 contain the older stuff too. BTW your going to have to delete all the stuff you got. There are even newer versions of the downloads.
SP1 Security Update versions. I already have them and updated my copy of the script. I am updating the APMs now.
DesertJerry: ya I figured that out a while ago. I thought I could use that type of detection in the registry. Guess it only works in areas that accept ANY.
Also... Any 32bit program can ready x64 registry with 32bit calls to registry as long as you route it properly. Current version of Autopatcher is setup to be able to make the reads as long as you tell it how to do it.
Edited by ViroMan, 31 March 2012 - 03:29 AM.
SP1 Security Update versions. I already have them and updated my copy of the script. I am updating the APMs now.
DesertJerry: ya I figured that out a while ago. I thought I could use that type of detection in the registry. Guess it only works in areas that accept ANY.
Also... Any 32bit program can ready x64 registry with 32bit calls to registry as long as you route it properly. Current version of Autopatcher is setup to be able to make the reads as long as you tell it how to do it.
Edited by ViroMan, 31 March 2012 - 03:29 AM.
ViroMan
31 Mar 2012
Alright I think I am done with this script now. It looks good for me. Someone give it a spin on another x64 system and a x86 system. If its good I will place in Official list and sign it.
Whatacrock
31 Mar 2012
ran apup1 with release2.list to download the visual C++ redistributable packages...downloaded fine
Ran autopatcher and when check the releases displayed the visual c++ packages in pretty blue... so it works fine on an x86 system.
Here's the spoiler for verification
Edited by Whatacrock, 31 March 2012 - 04:15 AM.
Ran autopatcher and when check the releases displayed the visual c++ packages in pretty blue... so it works fine on an x86 system.
Here's the spoiler for verification
Spoiler
Edited by Whatacrock, 31 March 2012 - 04:15 AM.
Whatacrock
31 Mar 2012
Not so good news for the x64 side.Clean installed Win XP Pro x64 on separate drive fitted in XP x86 machine, updated system with both autopatcher and windows update finally downloaded the visual c++ packages and reran ap
Selected 2005 2008 and 2010. Received syntax errors on 2005 and 2008(both x86 and x64),ap continues to try to install the packages,click the button and next syntax error appears,allowed ap to finish and rebooted, reran ap.Only 2010 x86 and x64 were showing in pretty blue, the others showed black. Tried running several times and same result on each run.
Is it really necessary to reboot system after only doing the visual C++ package ? I ask as ap when finished and click radio button wants to reboot.
Selected 2005 2008 and 2010. Received syntax errors on 2005 and 2008(both x86 and x64),ap continues to try to install the packages,click the button and next syntax error appears,allowed ap to finish and rebooted, reran ap.Only 2010 x86 and x64 were showing in pretty blue, the others showed black. Tried running several times and same result on each run.
Is it really necessary to reboot system after only doing the visual C++ package ? I ask as ap when finished and click radio button wants to reboot.
DesertJerry
31 Mar 2012
Not sure if the following will help or hinder everything but after I posted my findings last night I did some more looking through the registry (XP Pro w/SP3):
HKCR\Installer\Products\1D5E3C0FEDA1E123187686FED06E995A
ProductName=Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
HKCR\Installer\Products\5104B339816461748A822598CF3061F5\SourceList\Net\1=D:\Program Files\Common Files\DivX Shared\
ProductName=VC80CRTRedist - 8.0.50727.6195
HKCR\Installer\Products\6E58EC68CABDDFF39B774E7BF9389C90
ProductName=Microsoft Visual C++ 2008 Redistributable - KB2467174 - x86 9.0.30729.5570
HKEY_CLASSES_ROOT\Installer\Products\6E815EB96CCE9A53884E7857C57002F0
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
HKCR\Installer\Products\6F9E66FF7E38E3A3FA41D89E8A906A4A
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
HKCR\Installer\Products\B17E077734D20084C93BB5C6AABEBEAE
ProductName=RealNetworks - Microsoft Visual C++ 2008 Runtime
HKCR\Installer\Products\c1c4f01781cc94c4c8fb1542c0981a2a
ProductName=Microsoft Visual C++ 2005 Redistributable
HKCR\Installer\Products\CFD2C1F142D260E3CB8B271543DA9F98
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
HKCR\Installer\Products\CFE98E2070B7A5D4AA30E90C099241EE
ProductName=VC 9.0 Runtime
HKCR\Installer\Products\D33A333FC5212A23D8ECC5D54132E172
ProductName=Visual C++ 2008 x86 Runtime - (v9.0.30729)
HKCR\Installer\Products\F942F94A19C0F79468FD2B85E5E8677B
ProductName=Microsoft Visual C++ 2005 Redistributable
HKCR\Installer\Products\1D5E3C0FEDA1E123187686FED06E995A
ProductName=Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
HKCR\Installer\Products\5104B339816461748A822598CF3061F5\SourceList\Net\1=D:\Program Files\Common Files\DivX Shared\
ProductName=VC80CRTRedist - 8.0.50727.6195
HKCR\Installer\Products\6E58EC68CABDDFF39B774E7BF9389C90
ProductName=Microsoft Visual C++ 2008 Redistributable - KB2467174 - x86 9.0.30729.5570
HKEY_CLASSES_ROOT\Installer\Products\6E815EB96CCE9A53884E7857C57002F0
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
HKCR\Installer\Products\6F9E66FF7E38E3A3FA41D89E8A906A4A
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
HKCR\Installer\Products\B17E077734D20084C93BB5C6AABEBEAE
ProductName=RealNetworks - Microsoft Visual C++ 2008 Runtime
HKCR\Installer\Products\c1c4f01781cc94c4c8fb1542c0981a2a
ProductName=Microsoft Visual C++ 2005 Redistributable
HKCR\Installer\Products\CFD2C1F142D260E3CB8B271543DA9F98
ProductName=Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
HKCR\Installer\Products\CFE98E2070B7A5D4AA30E90C099241EE
ProductName=VC 9.0 Runtime
HKCR\Installer\Products\D33A333FC5212A23D8ECC5D54132E172
ProductName=Visual C++ 2008 x86 Runtime - (v9.0.30729)
HKCR\Installer\Products\F942F94A19C0F79468FD2B85E5E8677B
ProductName=Microsoft Visual C++ 2005 Redistributable
DesertJerry
31 Mar 2012
Booted into XP Pro x64 w/SP2 > Started AutoPatcher > Windows Addons.
Microsoft Visual C+++ 2010 Redistributable in blue - all other Visual C++ Redistributables (x64 and x86) in black.
Opened vcredist_2010_x64.apm in Notepad, opened Registry Editor-64bit and determined there was NO Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA5E371C-6333-3D8A-93A4-6FD5B20BCC6E} as shown in the APM file.
Opened Registry Editor-32bit and determined there was NO Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA5E371C-6333-3D8A-93A4-6FD5B20BCC6E} as shown in the APM file.
Opened the list of registry keys I had posted earlier and found that this key did not match the key I had posted: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
Coped my key into the APM file and saved it. Re-started AutoPatcher - still black.
Online > AutoPatcher forum > New stuff > APUP2 > downloaded new Visual C++ script dated 30 Mar 2012.
AutoPatcher > Windows Addons > Visual C++ blue except for 2008 SP1 Security x86 and 2005 SP1 Security x86. Check mark for both > next > Error message: Command line option syntax error. Type Command /? for Help > OK > Finished. Still black. One at a time - 2005 SP1 gave syntax eroor; 2008 SP1 no error but still black. Restart system. AutoPatcher > items still black.
Booted into Win7 Ultimate x64 w/SP1 > Started AutoPatcher > Windows Addons.
Only displayed Visual C++ Security Updates for x86 - NO x64 items listed.
Opened each APM file and changed:
[OperatingSystem]
WindowsVersion=XP_SP2_X64,2K3_SP2_X64,VISTA_X64,Win7_X64
SystemLanguage=ANY
to
[OperatingSystem]
WindowsVersion=XP_SP2_X64,2K3_SP2_X64,VISTA_X64,SEVEN_X64
SystemLanguage=ANY
Re-started AutoPatcher > all Visual C++ Security items now listed in blue.
Edited by DesertJerry, 31 March 2012 - 10:01 PM.
Microsoft Visual C+++ 2010 Redistributable in blue - all other Visual C++ Redistributables (x64 and x86) in black.
Opened vcredist_2010_x64.apm in Notepad, opened Registry Editor-64bit and determined there was NO Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA5E371C-6333-3D8A-93A4-6FD5B20BCC6E} as shown in the APM file.
Opened Registry Editor-32bit and determined there was NO Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA5E371C-6333-3D8A-93A4-6FD5B20BCC6E} as shown in the APM file.
Opened the list of registry keys I had posted earlier and found that this key did not match the key I had posted: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
Coped my key into the APM file and saved it. Re-started AutoPatcher - still black.
Online > AutoPatcher forum > New stuff > APUP2 > downloaded new Visual C++ script dated 30 Mar 2012.
AutoPatcher > Windows Addons > Visual C++ blue except for 2008 SP1 Security x86 and 2005 SP1 Security x86. Check mark for both > next > Error message: Command line option syntax error. Type Command /? for Help > OK > Finished. Still black. One at a time - 2005 SP1 gave syntax eroor; 2008 SP1 no error but still black. Restart system. AutoPatcher > items still black.
Booted into Win7 Ultimate x64 w/SP1 > Started AutoPatcher > Windows Addons.
Only displayed Visual C++ Security Updates for x86 - NO x64 items listed.
Opened each APM file and changed:
[OperatingSystem]
WindowsVersion=XP_SP2_X64,2K3_SP2_X64,VISTA_X64,Win7_X64
SystemLanguage=ANY
to
[OperatingSystem]
WindowsVersion=XP_SP2_X64,2K3_SP2_X64,VISTA_X64,SEVEN_X64
SystemLanguage=ANY
Re-started AutoPatcher > all Visual C++ Security items now listed in blue.
Edited by DesertJerry, 31 March 2012 - 10:01 PM.
ViroMan
01 Apr 2012
Product ID and installation ID seem to be two different things. If that path doesn't exist in your registry that version of install might not have installed properly(or mine)... look around in uninstall it has to be there if it was installed.
ohh.. damn... messed the detection up by using win7. Sorry that is in my new ap.
Ohh it is NOT needed to reboot after installing these. I did though because I thought my firewall depended on it... and it did. Didn't know I left that set on. I just reused an older APM.
Edited by ViroMan, 01 April 2012 - 12:51 AM.
ohh.. damn... messed the detection up by using win7. Sorry that is in my new ap.
Ohh it is NOT needed to reboot after installing these. I did though because I thought my firewall depended on it... and it did. Didn't know I left that set on. I just reused an older APM.
Edited by ViroMan, 01 April 2012 - 12:51 AM.
Whatacrock
04 Apr 2012
@ViroMan...any further progress on the visual C++ redistributable packages ??
ViroMan
04 Apr 2012
Nothing yet... DesertJerry reported it not working right for him due to the keys not being there. So we need to figure that out. I can't do anymore on my end. He says the keys are not there for his x64 but they are for mine. I need more cross checking for verification. I need someone else with an x64(doesn't have to be windows XP just any x64 system) system to help verify if either one of us has a bad install or the damn thing generates a different ID for different systems.
Edited by ViroMan, 04 April 2012 - 08:48 PM.
I need someone else with an x64(doesn't have to be windows XP just any x64 system) system to help verify if either one of us has a bad install or the damn thing generates a different ID for different systems.
Edited by ViroMan, 04 April 2012 - 08:48 PM.
DesertJerry
04 Apr 2012
Got blue everywhere.
vcredist_2005_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}
KeyName=DisplayVersion
KeyValue=8.0.61000
vcredist_2005_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
vcredist_2008_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
vcredist_2008_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4} <---Win7
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9BE518E6-ECC6-35A9-88E4-87755C07200F} <---XPPro and Win7
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
vcredist_2010_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
KeyName=DisplayVersion
KeyValue=10.0.40219
vcredist_2010_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
KeyName=DisplayVersion
KeyValue=10.0.40219
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
KeyName=DisplayVersion
KeyValue=10.0.40219
Hope this helps/
vcredist_2005_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}
KeyName=DisplayVersion
KeyValue=8.0.61000
vcredist_2005_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
KeyName=DisplayVersion
KeyValue=8.0.61001
vcredist_2008_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
vcredist_2008_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4} <---Win7
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9BE518E6-ECC6-35A9-88E4-87755C07200F} <---XPPro and Win7
KeyName=DisplayVersion
KeyValue=9.0.30729.6161
vcredist_2010_x64.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
KeyName=DisplayVersion
KeyValue=10.0.40219
vcredist_2010_x86.apm
[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
KeyName=DisplayVersion
KeyValue=10.0.40219
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
KeyName=DisplayVersion
KeyValue=10.0.40219
Hope this helps/
ViroMan
05 Apr 2012
ok, so things are fine now. hmm.. strange that your windows 7 has two entries for the same install though.
edit: Minor changes, new version up. If its good for both of you I will update main list.
Edited by ViroMan, 05 April 2012 - 03:03 AM.
edit: Minor changes, new version up. If its good for both of you I will update main list.
Edited by ViroMan, 05 April 2012 - 03:03 AM.
DesertJerry
05 Apr 2012
04 April > 2135 Qick check
Booted - XP Pro w/SP3 all blue
XP Pro x64 w/SP2 C++ 2008 SP1 x86 black - others blue
Selected program and opted to do a repair - still black. Have no idea why it has disappeared. Searched registry - gone; WTF?
Win7 Ultimate 64bit w/SP1 - all blue
Will be able to check more tomorrow.
Booted - XP Pro w/SP3 all blue
XP Pro x64 w/SP2 C++ 2008 SP1 x86 black - others blue
Selected program and opted to do a repair - still black. Have no idea why it has disappeared. Searched registry - gone; WTF?
Win7 Ultimate 64bit w/SP1 - all blue
Will be able to check more tomorrow.
Whatacrock
05 Apr 2012
Ran apup2 with release2 list to download updated script.
Ran ap on my x86 system and visual c++ showed black while 2008 and 2010 showed pretty blue.When tried installing 2005 I received the syntax error again.
Reran on x64 system script downloaded fine but on running ap only 2010 showed pretty blue, all others in black.
Tried running one by one and received the same syntax error on installing vc++ 2005 x64/x86.
VC++ 2008 refuses to install from autopatcher but I know that it was manually installed and shows up in program list for add and remove programs..
Attached screenshot
Edited by Whatacrock, 05 April 2012 - 07:28 AM.
Ran ap on my x86 system and visual c++ showed black while 2008 and 2010 showed pretty blue.When tried installing 2005 I received the syntax error again.
Reran on x64 system script downloaded fine but on running ap only 2010 showed pretty blue, all others in black.
Tried running one by one and received the same syntax error on installing vc++ 2005 x64/x86.
VC++ 2008 refuses to install from autopatcher but I know that it was manually installed and shows up in program list for add and remove programs..
Attached screenshot
Edited by Whatacrock, 05 April 2012 - 07:28 AM.
ViroMan
05 Apr 2012
What is this syntax error your getting? Ohh hmm.. perhaps the install commands are bad... leme check.
ohh hmm looks like it doesn't like the word /quite... it wants /qn what ever... I will change.
Edited by ViroMan, 05 April 2012 - 07:39 AM.
ohh hmm looks like it doesn't like the word /quite... it wants /qn what ever... I will change.
Edited by ViroMan, 05 April 2012 - 07:39 AM.
ViroMan
05 Apr 2012
OK I have updated the install commands to the ones Microsoft says should work. I haven't tested it out yet as im in the middle of gaming.
edit: Or not... something isn't taking... need more time.
Edited by ViroMan, 05 April 2012 - 07:50 AM.
edit: Or not... something isn't taking... need more time.
Edited by ViroMan, 05 April 2012 - 07:50 AM.
Whatacrock
05 Apr 2012
There was no description for the syntax error and here's a screenie of it.
Whatacrock
05 Apr 2012
ViroMan .....you are DA man!!!
Ran apup v1 and v2 to ensure I got the scripts..good so far.
Ran ap and selected the redistributables showing black .... when finished reran ap again and now all show in pretty blue(x86 system)
Shut system down reconnected the hdd with x64 ...booted up and repeated the process.
Reran ap and voila we have pretty blue for both x86 and x64.
I guess we can put this puppy to bed as part of the main common files.
Just be to be sure need someone else to verify my findings.
Here are the screen for add and remove programs x64 systerm ie before and after shots
[attachment=565:screenshot..jpg] before
[attachment=566:screenie.jpg] after
Edited by Whatacrock, 05 April 2012 - 09:44 AM.
Ran apup v1 and v2 to ensure I got the scripts..good so far.
Ran ap and selected the redistributables showing black .... when finished reran ap again and now all show in pretty blue(x86 system)
Shut system down reconnected the hdd with x64 ...booted up and repeated the process.
Reran ap and voila we have pretty blue for both x86 and x64.
I guess we can put this puppy to bed as part of the main common files.
Just be to be sure need someone else to verify my findings.
Here are the screen for add and remove programs x64 systerm ie before and after shots
[attachment=565:screenshot..jpg] before
[attachment=566:screenie.jpg] after
Edited by Whatacrock, 05 April 2012 - 09:44 AM.
ViroMan
05 Apr 2012
Well I would rather not place it in commons because its not really a common thing. To some people it would be and extra unneeded 34MB. If you mean place it in the main list then yes provided someone else agrees its working fine. Then it shall be done.
