> I clicked on install and it failed
it didn't showed here. but i'm talking only about seven
> hurricane force winds
the scary part was the noise in the windows... but some trees was ripped apart due that wind. some power lines too
> wild fires
i've saw some news about. the climate seems to be changing. to far worst in here, but for sure to worst in a lot of other places too
oh well, there's about 53 days to go yet until spring...
[]s
2
.NET Framework Addon Pack
Started by James, Oct 16 2008 12:03 PM
354 replies to this topic
#61
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 31 July 2010 - 09:55 PM
#62
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 06 October 2010 - 10:32 PM
script updated to fix an issue in Windows6.1-KB2416471-x64.apm
[]s
[]s
#63
-
- Members
-
- 91 posts
Advanced Member
- Gender:Male
- Location:Michigan
Posted 07 October 2010 - 05:53 PM
I'm getting a verification error with the .NET release since last night. Just letting you know. 
Plus, in regard to .NET, just a question about version numbers. Using AutoPatcher, I'm showing Microsoft .NET Framework 4 in blue. Windows Update updated my .NET Framework this past month with Security Update 3.5.1 (KB241671-x64). So, now .. Autopatcher shows Microsoft .NET Framework 4 in blue and the Microsoft .NET Framework 3.5.1 security update in blue ... and Microsoft .NET Framework 4 security update (KB2416472-x64) shows as black. Any ideas as to why this happened? I'm running Win7 Pro 64.
Spoiler
Plus, in regard to .NET, just a question about version numbers. Using AutoPatcher, I'm showing Microsoft .NET Framework 4 in blue. Windows Update updated my .NET Framework this past month with Security Update 3.5.1 (KB241671-x64). So, now .. Autopatcher shows Microsoft .NET Framework 4 in blue and the Microsoft .NET Framework 3.5.1 security update in blue ... and Microsoft .NET Framework 4 security update (KB2416472-x64) shows as black. Any ideas as to why this happened? I'm running Win7 Pro 64.
Edited by dfdff3000, 07 October 2010 - 06:08 PM.
#64
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 07 October 2010 - 07:45 PM
that verification issue seems to be only an issue related to the file size. no problem, i will fix it in 1h our so
> Any ideas as to why this happened?
yes. the .net updates aren't cumulative. .net 4 doesn't replace .net 3.5, etc. so, if autopatcher shows Microsoft .NET Framework 4 in blue, you have it installed. also you has this one, you will require all the .net 4 updates, like KB2416472-x64. as this one is showing in black, this one isn't installed yet or there's an issue related to the install string. no problem, i can check that
[]s
> Any ideas as to why this happened?
yes. the .net updates aren't cumulative. .net 4 doesn't replace .net 3.5, etc. so, if autopatcher shows Microsoft .NET Framework 4 in blue, you have it installed. also you has this one, you will require all the .net 4 updates, like KB2416472-x64. as this one is showing in black, this one isn't installed yet or there's an issue related to the install string. no problem, i can check that
[]s
#65
-
- Veterans
-
- 1,460 posts
audi 5k
- Gender:Male
Posted 07 October 2010 - 07:57 PM
windows_dotnet.7z is offline so Cristiano may be looking into something, should fix the size issue in the script as well.
I'm not sure why security update for .NET 3.5 (KB241671-x64) would install .NET 4, doesn't sound very likely to me.
KB2416472-x64 is a security update for .NET 4, until you install the patch it will stay black unless WU/MU installs it for you.
You can try this free portable tool and have it check to see what .NET you have installed - .NET Version Detector
Note: I left my post even though while I was typing someone posted ahead of me
I'm not sure why security update for .NET 3.5 (KB241671-x64) would install .NET 4, doesn't sound very likely to me.
KB2416472-x64 is a security update for .NET 4, until you install the patch it will stay black unless WU/MU installs it for you.
You can try this free portable tool and have it check to see what .NET you have installed - .NET Version Detector
Note: I left my post even though while I was typing someone posted ahead of me
Edited by gUiTaR_mIkE, 07 October 2010 - 07:59 PM.
#66
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 07 October 2010 - 09:37 PM
well, in deed one file was missing at our servers. fixed
as for kb2416471 x64:
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=Package_for_kb2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
FileVersion=ANY
and KB2416472-x64:
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Extended\KB2416472
KeyName=PackageVersion
KeyValue=1
with those detections, it should be showing as this if installed. if not, then it should be in black
[]s
as for kb2416471 x64:
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=Package_for_kb2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
FileVersion=ANY
and KB2416472-x64:
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Extended\KB2416472
KeyName=PackageVersion
KeyValue=1
with those detections, it should be showing as this if installed. if not, then it should be in black
[]s
#67
-
- Members
-
- 91 posts
Advanced Member
- Gender:Male
- Location:Michigan
Posted 07 October 2010 - 11:00 PM
@gUiTaR_mIkE
No matter how many times I think I know what I mean to say, it never comes out the way I meant it, lol. I thought I already had .NET 4. It was just more a case of wondering why the .NET 4 update wasn't applied and why 3.5.1 was instead. BTW, it was Windows update that installed 3.5.1. You and Cristiano frequently post responses at the same time. It's all good
.. all help is appreciated. I downloaded that program you recommended and these were the results.
@Cristiano
Thanks for fixing the apup .NET verification error! I'm still showing KB2416472-x64 in black .. and it won't install using autopatcher.
This is all I could find in my windows update install history in regard to .NET. Does it make any sense?
No matter how many times I think I know what I mean to say, it never comes out the way I meant it, lol. I thought I already had .NET 4. It was just more a case of wondering why the .NET 4 update wasn't applied and why 3.5.1 was instead. BTW, it was Windows update that installed 3.5.1. You and Cristiano frequently post responses at the same time. It's all good
.. all help is appreciated. I downloaded that program you recommended and these were the results.
Spoiler
@Cristiano
Thanks for fixing the apup .NET verification error! I'm still showing KB2416472-x64 in black .. and it won't install using autopatcher.
This is all I could find in my windows update install history in regard to .NET. Does it make any sense?
Spoiler
#68
-
- Veterans
-
- 1,460 posts
audi 5k
- Gender:Male
Posted 07 October 2010 - 11:31 PM
However it was installed it looks as if you have .NET 4.0 Client installed.
-> I'm still showing KB2416472-x64 in black .. and it won't install using autopatcher.
Is it not installed or is it that AutoPatcher is not detecting the applied update? Did you get any error messages while trying to install? Does WU detect it as installed. See if you can search for the log file on your system - use the patch kb# - what does it say, any messages about wrong patch for this system?
The update either does not apply to your system which would mean it is not installed or it actually installed but the detections are not good in which they need to be fixed in the .apm file (module)?
-> I'm still showing KB2416472-x64 in black .. and it won't install using autopatcher.
Is it not installed or is it that AutoPatcher is not detecting the applied update? Did you get any error messages while trying to install? Does WU detect it as installed. See if you can search for the log file on your system - use the patch kb# - what does it say, any messages about wrong patch for this system?
The update either does not apply to your system which would mean it is not installed or it actually installed but the detections are not good in which they need to be fixed in the .apm file (module)?
#69
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 07 October 2010 - 11:47 PM
> I'm still showing KB2416472-x64 in black .. and it won't install using autopatcher.
i've uninstalled this update just to be sure. at an first run, it was showing as not installed, as expected. after that, i've selected this one to be installed. the result was blue. so, the install command is ok and the detection also is. as stated in here, KB2416472-x64 is an update for Windows 7 for x64-based Systems, Microsoft .NET Framework 4.0. so, i'm not really sure why it isn't working for you, but the .net detection that i got in here isn't the same that you got:
<32Bit>
2.0.50727.4952
->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.0.30319.1
->C:\Windows\Microsoft.NET\Framework\v4.0.30319
<64Bit>
2.0.50727.4952
->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.0.30319.1
->C:\Windows\Microsoft.NET\Framework64\v4.0.30319
< Installed .NET Frameworks >
.NET FW 2.0 SP 2
.NET FW 3.0 SP 2
.NET FW 3.5 SP 1
.NET FW 4.0 Client
.NET FW 4.0 Full
given that, you only have the client version (that is installed through WU) and i have client and full (that are installed through the standalone installer that autopatcher has). it's possible that this update can't work in your system due that difference, but in a silent install, you won't see that. so please, look at modules\Components\__dotnet\NDP40-KB2416472-x64.apm_files and try to run NDP40-KB2416472-x64.exe. if there's something that ms isn't saying about this update, installing manually will point
> Does it make any sense?
it only states that you only have the client version of this one. it's possible that this update only works with the full version, but if this is the case, then we may have an problem, because autopatcher can detect .net 4, but doesn't know the difference between the client and full version. also, ms doesn't say that the update applies only to the full version
[]s
i've uninstalled this update just to be sure. at an first run, it was showing as not installed, as expected. after that, i've selected this one to be installed. the result was blue. so, the install command is ok and the detection also is. as stated in here, KB2416472-x64 is an update for Windows 7 for x64-based Systems, Microsoft .NET Framework 4.0. so, i'm not really sure why it isn't working for you, but the .net detection that i got in here isn't the same that you got:
<32Bit>
2.0.50727.4952
->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.0.30319.1
->C:\Windows\Microsoft.NET\Framework\v4.0.30319
<64Bit>
2.0.50727.4952
->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.0.30319.1
->C:\Windows\Microsoft.NET\Framework64\v4.0.30319
< Installed .NET Frameworks >
.NET FW 2.0 SP 2
.NET FW 3.0 SP 2
.NET FW 3.5 SP 1
.NET FW 4.0 Client
.NET FW 4.0 Full
given that, you only have the client version (that is installed through WU) and i have client and full (that are installed through the standalone installer that autopatcher has). it's possible that this update can't work in your system due that difference, but in a silent install, you won't see that. so please, look at modules\Components\__dotnet\NDP40-KB2416472-x64.apm_files and try to run NDP40-KB2416472-x64.exe. if there's something that ms isn't saying about this update, installing manually will point
> Does it make any sense?
it only states that you only have the client version of this one. it's possible that this update only works with the full version, but if this is the case, then we may have an problem, because autopatcher can detect .net 4, but doesn't know the difference between the client and full version. also, ms doesn't say that the update applies only to the full version
[]s
#70
-
- Members
-
- 91 posts
Advanced Member
- Gender:Male
- Location:Michigan
Posted 08 October 2010 - 12:02 AM
I'm pretty sure KB2416472-x64 and KB2416471-x64 were released the same day. WU installed KB2416471-x64. It should be one or the other, correct? Not both? Orrrrrrrrrr ... from Cristiano ...
> Any ideas as to why this happened?
yes. the .net updates aren't cumulative. .net 4 doesn't replace .net 3.5, etc. so, if autopatcher shows Microsoft .NET Framework 4 in blue, you have it installed. also you has this one, you will require all the .net 4 updates, like KB2416472-x64. as this one is showing in black, this one isn't installed yet or there's an issue related to the install string. no problem, i can check that
Does that mean I need both updates??
In the 2nd spoiler from my previous post I attempted to show any and all .NET updates WU showed as installed - which included Microsoft .NET Framework 4 Client Profile for Windows 7 x64-based Systems (KB982670).
Using AutoPatcher, no error message while trying to install. The only thing that was out of the ordinary was that it estimated the time to install as a couple of minutes, but then immediately said it was finished (and then needed reboot). After reboot, same situation. Sure looks like it's not installed.
@Cristiano .. just followed your instructions and attempted to manually install it by running NDP40-KB2416472-x64.exe. I got the following message: KB2416472 does not apply, or is blocked by another condition on your computer.
> Any ideas as to why this happened?
yes. the .net updates aren't cumulative. .net 4 doesn't replace .net 3.5, etc. so, if autopatcher shows Microsoft .NET Framework 4 in blue, you have it installed. also you has this one, you will require all the .net 4 updates, like KB2416472-x64. as this one is showing in black, this one isn't installed yet or there's an issue related to the install string. no problem, i can check that
Does that mean I need both updates??
In the 2nd spoiler from my previous post I attempted to show any and all .NET updates WU showed as installed - which included Microsoft .NET Framework 4 Client Profile for Windows 7 x64-based Systems (KB982670).
Spoiler
Using AutoPatcher, no error message while trying to install. The only thing that was out of the ordinary was that it estimated the time to install as a couple of minutes, but then immediately said it was finished (and then needed reboot). After reboot, same situation. Sure looks like it's not installed.
@Cristiano .. just followed your instructions and attempted to manually install it by running NDP40-KB2416472-x64.exe. I got the following message: KB2416472 does not apply, or is blocked by another condition on your computer.
Edited by dfdff3000, 08 October 2010 - 12:10 AM.
#71
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 08 October 2010 - 12:11 AM
> It should be one or the other, correct? Not both?
that's the point: if ms states that the update is for .net 4, if you have any version of it, then WU should offer both updates, but a lot of times, WU miss some updates
> Does that mean I need both updates??
probably true, at least according to MS10-070, that is linked at #69
> Using AutoPatcher, no error message while trying to install
autopatcher deploys all the updates in silent mode. due that, no error messages at all. this kind of message only shows when manually installing the update
the install time isn't an concern at all, because it is a lot shorter or a lot longer according to you computer specs. but to test the issue, only trying deploy the update manually (just select and hit enter, then check an "i agree" and wait)
[]s
that's the point: if ms states that the update is for .net 4, if you have any version of it, then WU should offer both updates, but a lot of times, WU miss some updates
> Does that mean I need both updates??
probably true, at least according to MS10-070, that is linked at #69
> Using AutoPatcher, no error message while trying to install
autopatcher deploys all the updates in silent mode. due that, no error messages at all. this kind of message only shows when manually installing the update
the install time isn't an concern at all, because it is a lot shorter or a lot longer according to you computer specs. but to test the issue, only trying deploy the update manually (just select and hit enter, then check an "i agree" and wait)
[]s
#72
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 08 October 2010 - 12:15 AM
> I got the following message: KB2416472 does not apply, or is blocked by another condition on your computer
that's the reason why it doesn't work and why it never will show as installed: despite ms say that this one is an .net 4 update, this one probably is only for the full version. the problem: i'm not sure how make the module not to be showed if the full version isn't present. to do that, we require to know about any file that is present only in the full version. i will try find it, but i'm not sure if i will be able to
thanks
[]s
that's the reason why it doesn't work and why it never will show as installed: despite ms say that this one is an .net 4 update, this one probably is only for the full version. the problem: i'm not sure how make the module not to be showed if the full version isn't present. to do that, we require to know about any file that is present only in the full version. i will try find it, but i'm not sure if i will be able to
thanks
[]s
#73
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 08 October 2010 - 12:35 AM
one idea for an detection: please look at C:\Users\your user name\AppData\Local\Temp for ASPNETSetup and open that file. this log may say something about the issue
[]s
[]s
#74
-
- Members
-
- 91 posts
Advanced Member
- Gender:Male
- Location:Michigan
Posted 08 October 2010 - 12:43 AM
You are correct Cristiano. It appears all the confusion was because I was running the client version of .NET 4 and not the full. I just now installed the full .NET 4 version and then checked with WU. It finally showed KB2416472 as being available for it. I installed KB2416472 using AutoPatcher instead and then rebooted. All .NET updates are showing as blue now. Many thanks for your help gentlemen.
Crap, while I was doing all of that (and typing this) I see you made another post Cristiano. I'm guessing anything in that Temp file would pretty much be useless now?
Crap, while I was doing all of that (and typing this) I see you made another post Cristiano. I'm guessing anything in that Temp file would pretty much be useless now?
Edited by dfdff3000, 08 October 2010 - 12:45 AM.
#75
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 08 October 2010 - 12:51 AM
no, that temp file still is in there, but probably as ASPNETSetup_00011.log or something. as you already have deployed that update, please look for the last number -1, like ASPNETSetup_00010.log. in here, that log looks for this file: aspnet_isapi.dll. if this file isn't present in a client only version, then this could work as an detection
[]s
[]s
#76
-
- Members
-
- 91 posts
Advanced Member
- Gender:Male
- Location:Michigan
Posted 08 October 2010 - 01:16 AM
I'm showing 4 log files. ASPNETSetup_00000 through ASPNETSetup_00003. All of them appear to be looking for aspnet_isapi.dll. They seem to be in pairs though?
ASPNETSetup_00000 and ASPNETSetup_00001 are 15 seconds apart.
ASPNETSetup_00000 looks for aspnet_isapi.dll in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
ASPNETSetup_00001 looks for aspnet_isapi.dll in C:\Windows\Microsoft.NET\Framework\v4.0.30319\
ASPNETSetup_00002 and ASPNETSetup_00003 are 8 seconds apart.
ASPNETSetup_00002 looks for aspnet_isapi.dll in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\
ASPNETSetup_00003 looks for aspnet_isapi.dll in c:\Windows\Microsoft.NET\Framework\v4.0.30319\
ASPNETSetup_00000 and ASPNETSetup_00001 are 15 seconds apart.
ASPNETSetup_00000 looks for aspnet_isapi.dll in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
ASPNETSetup_00001 looks for aspnet_isapi.dll in C:\Windows\Microsoft.NET\Framework\v4.0.30319\
ASPNETSetup_00002 and ASPNETSetup_00003 are 8 seconds apart.
ASPNETSetup_00002 looks for aspnet_isapi.dll in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\
ASPNETSetup_00003 looks for aspnet_isapi.dll in c:\Windows\Microsoft.NET\Framework\v4.0.30319\
#77
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 08 October 2010 - 02:05 AM
i'm not sure. but to check that, an test with an clean system must be done. i may have some free time this weekend, then i will set an clean vm and deploy only the client version. then, compare the files, check for possible restrictions... but this surely will take time and i don't know if this is possible. but to be sure, only trying. so...
[]s
[]s
#78
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 12 October 2010 - 01:27 AM
ok, i had to do an clean install to be sure about the differences between .net 4 full and client, but i think that i've found it. in deed, that aspnet_isapi.dll seems to exist only in the full version of .net 4. so, easy solution: (just edit KB2416472 and paste it at the end of SystemComponents)
[SystemComponents]
ComponentFile=windows:\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
with that in the module, an system that doesn't have aspnet_isapi.dll will not load KB2416472. can someone else confirm if that restriction works, please?
thanks
[]s
[SystemComponents]
ComponentFile=windows:\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
with that in the module, an system that doesn't have aspnet_isapi.dll will not load KB2416472. can someone else confirm if that restriction works, please?
thanks
[]s
#79
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 14 October 2010 - 09:29 PM
done, .net script updated. changes:
# 2010-10-14: (Cristiano) +KB2160841; KB2416472 restricted to .net 4 full
[]s
# 2010-10-14: (Cristiano) +KB2160841; KB2416472 restricted to .net 4 full
[]s
#80
-
- Veterans
-
- 1,460 posts
audi 5k
- Gender:Male
Posted 15 October 2010 - 09:23 AM
...a small fix to the .NET script is needed,
from - DetectFile=autopatcher:\modules\Components\__dotnet\NDP40-KB2160841-x64_files\NDP40-KB2160841-x64.exe
to - DetectFile=autopatcher:\modules\Components\__dotnet\NDP40-KB2160841-x64.apm_files\NDP40-KB2160841-x64.exe
The release is Unofficial without the change and the .md5 can't find the file, edit the folder name and the release is Official and the .md5 finds all files
from - DetectFile=autopatcher:\modules\Components\__dotnet\NDP40-KB2160841-x64_files\NDP40-KB2160841-x64.exe
to - DetectFile=autopatcher:\modules\Components\__dotnet\NDP40-KB2160841-x64.apm_files\NDP40-KB2160841-x64.exe
The release is Unofficial without the change and the .md5 can't find the file, edit the folder name and the release is Official and the .md5 finds all files
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
