Jump to content


Windows XP 32 SP3 .Net 4.0 Issue


15 replies to this topic

#1 Orkon

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 23 February 2013 - 11:03 PM

Hi Guys

When patching a Windows XP SP3 autopatcher doesn't appear to allow .NET 4.0 to be installed.

What i've done
- Run APUP just for .Net x86 with logging on - everything verified
- Run autopatcher - .Net 4.0 was not an option.
- Went into the Modules folder and found the .net 4.0 full install - ran it manually
- Re-Ran autopatcher - .Net 4.0 is now in the tree and patchable.

Is the .net 4.0 supposed to be installable as part of the autopatcher for XP SP3?

Thanks
Ork

Edited by Orkon, 23 February 2013 - 11:04 PM.


#2 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 24 February 2013 - 12:12 AM

It should have shown up if you didn't have 4.5 installed. What was offered?
Do you see .NET 1.1 being offered?
Can you post a screenshot?

edit:
Another possibility why 4.0 may not have been offered is if you had a version of
PresentationFramework.Aero.dll on your system that was version 4.0.30319.17929 or greater.

Edited by click-click, 24 February 2013 - 02:18 PM.


#3 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 24 February 2013 - 03:39 AM

4.5 is only for Vista/Win7

Later:

XP Pro x64 w/SP2 #1 and #2

Autopatcher v 5.7.29 on both systems.

Microsoft Windows - Updated Components

#1 system lists .Net Framework 4.0 and all sub-items blue
#2 system does not list .Net Framework 4.0 and it will not install when attempt made using DotNetFx40_Client_x86_x64.exe - get error message "Blocking Issues: The setup cannot run in compatibility mode. (Unable to resolve issue - tried searching online and in Microsoft forums.)

Updated Components does not list .Net Framework 1.1 as being installed though Add or Remove Programs in both does list Microsft .Net Framework 1.1 (including three security updates)

Edited by DesertJerry, 24 February 2013 - 04:59 AM.


#4 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 24 February 2013 - 11:55 AM

Yes. I realize 4.5 is not for XP. I've mentioned it myself several times.Posted Image I must have had a senior moment trying to indicate what might be the cause of the problem.Posted Image Seems to be system related. Try this.

Edited by click-click, 24 February 2013 - 01:52 PM.


#5 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 24 February 2013 - 12:01 PM

>XP Pro x64 w/SP2 #1 and #2
Does that mean you have two systems that are the same and one shows it and the other doesn't?

#6 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 24 February 2013 - 10:12 PM

View Postclick-click, on 24 February 2013 - 12:01 PM, said:

>XP Pro x64 w/SP2 #1 and #2
Does that mean you have two systems that are the same and one shows it and the other doesn't?
Yes, I have two separate systems - as mentioned #2 has issues with installing .Net Framework 4.0 on XP Pro x64 - #1 is just fine. The try this link (above) leads to a HyperV and Win7 answer - not applicable

Edited by DesertJerry, 24 February 2013 - 10:15 PM.


#7 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 24 February 2013 - 11:39 PM

The title is misleading. Instead of assuming it is not applicable, please try it and then you will know for a fact that it
either helps or it doesn't and then you can supply us with some constructive feedback on the results. Sometimes I wonder why I even bother ...

Edited by click-click, 25 February 2013 - 12:17 AM.


#8 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 25 February 2013 - 05:35 AM

The information provided in the link does not apply - in the \Persisted location or unchecking Compatibility Mode (which is and was always unchecked); which, after I read the posting, is a repeat of suggestions I tried previously - as I mentioned earlier I tried the Microsoft forums (which was full of the same information suggested in the link) and using online searches - I bother because some people seem to not read all the information provided and a reminder is necessary.

#9 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 25 February 2013 - 06:28 AM

> (Unable to resolve issue - tried searching online and in Microsoft forums.)

That is all you said. You did not say you tried anything. You made a statement that left it unclear as to what you did to solve your problem if anything. Now you come out and say you tried all that already. Why did you not mention before that you tried various suggestions which were of no help? This would have saved me some time trying to find a solution for you.

Edited by click-click, 25 February 2013 - 06:43 AM.


#10 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 26 February 2013 - 08:32 PM

Go back and re-read posting #3 - I said the same thing there about online searches and Microsoft forums

#11 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 26 February 2013 - 09:06 PM

View PostDesertJerry, on 26 February 2013 - 08:32 PM, said:

Go back and re-read posting #3 - I said the same thing there about online searches and Microsoft forums

Go back and re-read posting #9.
I quoted you from your post #3 in my post #9. All you said was that you could not resolve the issue searching the web.
You said zero, nada, zilch about trying anything out. That was my whole point. That is why I asked you to try the
link I posted. I guess I did not like the way you answered: "The try this link (above) leads to a HyperV and Win7 answer - not applicable" That sounded a bit arrogant to me since you did not even bother telling me why it did not apply. I had to push you for an answer.

Edited by click-click, 26 February 2013 - 09:12 PM.


#12 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 26 February 2013 - 10:41 PM

What an arrogant statement

#13 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 26 February 2013 - 10:55 PM

Good, now you understand. Posted Image.

#14 Orkon

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 01 March 2013 - 11:02 AM

View Postclick-click, on 24 February 2013 - 12:12 AM, said:

It should have shown up if you didn't have 4.5 installed. What was offered?
Do you see .NET 1.1 being offered?
Can you post a screenshot?

edit:
Another possibility why 4.0 may not have been offered is if you had a version of
PresentationFramework.Aero.dll on your system that was version 4.0.30319.17929 or greater.

Sorry for delay in responding. I had options in the tree of 1.1, 2 and 3.5, but not 4.0. As mentioned I ran the 4.0 full install manually from the AP folders and after that the node appeared in autopatcher.

Even if the version of the dll mentioned is as you said, why wouldn't the option to install be there if 4.0 has not been installed?

I've got 2 more systems that need updating. I'll try and get the information from those to give some feedback.

Thanks for your assistance

Ork

#15 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 01 March 2013 - 07:09 PM

The dll I mentioned is used to decide whether to suppress showing 4.0. Normally when 4.5 is installed (which has this version of the dll, AP should not show 4.0 since that version has been superseded by 4.5. This could have been one of the reasons why 4.0 did not show. I was only mentioning reasons why this may have happened. I don't know what is causing this on your system since 4.5 is not currently supported on XP. Also, is your system 32-bit or 64-bit?

Edited by click-click, 01 March 2013 - 07:09 PM.


#16 Orkon

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 01 March 2013 - 11:27 PM

Hi Click-Click

System is XP SP3 x86 (32 bit).

Ork





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users