Is .NET Framework 4.5/4.5.1 automatically installed by WU on Vista/7?


Recommended Posts

It's offered as critical update, but not automatically installed.

 

Since it's a superset of .NET 4.0 ff I would recommend installing it. Saves you from having to wait for a metric ton of .NET 4 updates to install.

It's offered as critical update, but not automatically installed.

 

Since it's a superset of .NET 4.0 ff I would recommend installing it. Saves you from having to wait for a metric ton of .NET 4 updates to install.

 

If critical updates aren't automatically installed (unless deselected) then which ones are? Catastrophic ones? :O

Don't modern versions of Windows throw a warning telling you to install the newer versions of .net anyway when you try to run the assemblies?

Yes they show a warning but installing a framework with all the updates can take up to an hour so when switching to a newer version I first have to consider if it would become a major inconvenience for most of the users or not.

 

I'm pretty sure Windows automatically installed some of newer frameworks (3.5/3.5.1 for sure if 2.0 or 3.0 is installed; I think I also saw 4.0 but I don't know if there were related conditions) but I never bothered checking the updates when setting up computers/VMs.

 

I would be much happier if I could use 4.5.1, or even 4.5 for having the better WPF controls available now that XP support is being discontinued (4.5 is not available on XP so it was a major issue until now). WPF on 3.5 and somewhat also on 4.0 can be some kind of a nightmare from hell.

Yes they show a warning but installing a framework with all the updates can take up to an hour so when switching to a newer version I first have to consider if it would become a major inconvenience for most of the users or not.

 

I'm pretty sure Windows automatically installed some of newer frameworks (3.5/3.5.1 for sure if 2.0 or 3.0 is installed; I think I also saw 4.0 but I don't know if there were related conditions) but I never bothered checking the updates when setting up computers/VMs.

 

I would be much happier if I could use 4.5.1, or even 4.5 for having the better WPF controls available now that XP support is being discontinued (4.5 is not available on XP so it was a major issue until now). WPF on 3.5 and somewhat also on 4.0 can be some kind of a nightmare from hell.

 

An hour is not a typical install time. With XP support discontinued, you shouldn't be targeting 4.0 (a known buggy version of .net) unless it is a client requirement.

An hour is not a typical install time. With XP support discontinued, you shouldn't be targeting 4.0 (a known buggy version of .net) unless it is a client requirement.

That only if you consider installing only the framework, but there are also all the related service packs, updates, etc. that are extremely slow to install (plus the download times). Ngen trashing the hard drive for a while after the install and after most of the updates can also be quite the annoyance. For now I never had any particular problem with 4.0 and would still prefer it to 3.5 anyday but that's because I wouldn't use WPF on any of both.

That only if you consider installing only the framework, but there are also all the related service packs, updates, etc. that are extremely slow to install (plus the download times). Ngen trashing the hard drive for a while after the install and after most of the updates can also be quite the annoyance. For now I never had any particular problem with 4.0 and would still prefer it to 3.5 anyday but that's because I wouldn't use WPF on any of both.

 

I've never had an issue with installing it or updates. I think you are mostly referring to the time it took 4.0 to pre-cache everything (read as: compile all of its assemblies into native code for your PC).

 

Targeting 4.0 is in generally a bad idea unless you know what you are doing. Remember, 4.5 is an in place upgrade of 4.0 which means that if you test a 4.0 target on a 4.5 install, you will be using the 4.5 library assemblies which have fixes for numerous defects over the 4.0 library assemblies. This means you will never exhibit broken behavior caused by 4.0 bugs. This is the fundamental reason why you shouldn't be targeting 4.0: because it leads to bugs and breakage that you cannot test for unless you are actually developing using the 4.0 platform directly.

As already been answered, .NET 4.0 and 4.5 are not automatically available on Windows Vista and 7. Available as updates, but as a developer, you shouldn't count on that.

 

However, Windows Vista and 7 do have versions of .NET installed. They both have .NET 2.0 (Vista has 2.0 SP1, and 7 2.0 SP2), and is irremovable, meaning you can always target it and expect it to work. Of course, WPF wasn't added until 3.0 or 3.5, so... :/ Vista and 7 also have .NET 3.0 and 3.5 installed, respectively, but can be removed, so, again, you shouldn't count on that.

 

Windows 8 has .NET 4.5 included, irremovably, and Windows 8.1 has 4.5.1. So at least developing for Windows 8 and later, you won't have to worry about the end user installing anything to get it to work. (Unless you are targeting a pre-4.0 version of .NET)

I've never had an issue with installing it or updates. I think you are mostly referring to the time it took 4.0 to pre-cache everything (read as: compile all of its assemblies into native code for your PC).

 

I'm referring to all of the time wasted. Download time, install time, updating time, most users don't have an high-end pc and it would take a lot of time. That also providing the users won't get tricked by those annoying adware-infested spammy search engine results in the process.

 

Targeting 4.0 is in generally a bad idea unless you know what you are doing. Remember, 4.5 is an in place upgrade of 4.0 which means that if you test a 4.0 target on a 4.5 install, you will be using the 4.5 library assemblies which have fixes for numerous defects over the 4.0 library assemblies. This means you will never exhibit broken behavior caused by 4.0 bugs. This is the fundamental reason why you shouldn't be targeting 4.0: because it leads to bugs and breakage that you cannot test for unless you are actually developing using the 4.0 platform directly.

 

Between 3.5 and 4.0 I'd rather pick 4.0 anyday, I've used it since it was released and I don't remember any particular issue (maybe a bit worse memory management) however I never used WPF with it because of the horrible performance, I only started using WPF after 4.5 came out.

 

As already been answered, .NET 4.0 and 4.5 are not automatically available on Windows Vista and 7. Available as updates, but as a developer, you shouldn't count on that.

 

My question was whether those updates are actually installed or not, because I have confused memories about that. I'm pretty sure I saw 4.0 automatically being checked on some machines but I'm also sure I saw Windows XP installing framework 3.5 for no reason at all (completely clean install with no other frameworks installed).

 

However, Windows Vista and 7 do have versions of .NET installed. They both have .NET 2.0 (Vista has 2.0 SP1, and 7 2.0 SP2), and is irremovable, meaning you can always target it and expect it to work. Of course, WPF wasn't added until 3.0 or 3.5, so... :/ Vista and 7 also have .NET 3.0 and 3.5 installed, respectively, but can be removed, so, again, you shouldn't count on that.

 

Windows 8 has .NET 4.5 included, irremovably, and Windows 8.1 has 4.5.1. So at least developing for Windows 8 and later, you won't have to worry about the end user installing anything to get it to work. (Unless you are targeting a pre-4.0 version of .NET)

 

I do know Vista and 7 come with framework 2.0/3.5 and was previously targeting 3.5 for that reason, because every 2.0 install (on XP and Vista) was automatically turned into 3.5 by Windows Update so it became a common platform for all the OS versions. If Windows Update did the same with 4.5 or 4.5.1 now that I can stop caring about XP support I'd happily switch to 4.5/4.5.1. But can somebody confirm that?

My question was whether those updates are actually installed or not, because I have confused memories about that. I'm pretty sure I saw 4.0 automatically being checked on some machines but I'm also sure I saw Windows XP installing framework 3.5 for no reason at all (completely clean install with no other frameworks installed).

 

 

I do know Vista and 7 come with framework 2.0/3.5 and was previously targeting 3.5 for that reason, because every 2.0 install (on XP and Vista) was automatically turned into 3.5 by Windows Update so it became a common platform for all the OS versions. If Windows Update did the same with 4.5 or 4.5.1 now that I can stop caring about XP support I'd happily switch to 4.5/4.5.1. But can somebody confirm that?

It's already been answered in this thread: 4.5 is not installed automatically on 7. Unless the behavior has changed with the 4.5.1 release, that is still the case. You could easily roll a temporary VM with 7 to test though. That's what I would I do if it were me

It's already been answered in this thread: 4.5 is not installed automatically on 7. Unless the behavior has changed with the 4.5.1 release, that is still the case. You could easily roll a temporary VM with 7 to test.

^ that - it is offered as important (not critical as I mistakenly wrote above) update, but not installed automatically on Windows 7.

It's already been answered in this thread: 4.5 is not installed automatically on 7. Unless the behavior has changed with the 4.5.1 release, that is still the case. You could easily roll a temporary VM with 7 to test though. That's what I would I do if it were me

I did some test installs on a VM and can confirm that:

- WU (now) doesn't install any newer framework on a clean XP SP3 install, with or without the included 1.1 installed.

- WU doesn't install any newer framework on a clean Windows 7 install (3.5 preinstalled). Windows Update only shows 4.5.1 (4.5 is not shown) as a recommended update (not important nor critical) in the optionals tab with no changes if I install 4.0 (client or full(extended)) or 4.5.

I did some test installs on a VM and can confirm that:

- WU (now) doesn't install any newer framework on a clean XP SP3 install, with or without the included 1.1 installed.

- WU doesn't install any newer framework on a clean Windows 7 install (3.5 preinstalled). Windows Update only shows 4.5.1 (4.5 is not shown) as a recommended update (not important nor critical) in the optionals tab with no changes if I install 4.0 (client or full(extended)) or 4.5.

 

What about if you install SP1? Does it give you 4.0 then automatically with that?

What about if you install SP1? Does it give you 4.0 then automatically with that?

Sorry I forgot to mention I used a Windows 7 SP1 disc to install. I also installed all the batches of security updates for each framework to be sure nothing changed.

 

As last thing I enabled Microsoft Update and now the update is listed as important (not in the optionals tab but also not selected) because when it's set up it enables the setting to have recommended updates considered as important.

Don't assume anything about the older .NET versions with the newer OSes.  For example, Server 2012 ships with 3.5, but you have to go to "Turn Windows features on or off" to install them.  Then you have to wait for the updates to install, then the updates to the updates, then...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • They've already bought Clipchamp, replaced Movie Maker with it, and made it worse in the end 🤣
    • Microsoft doesn't label their download like 2026.09.07. Their page only says updated on July 9, 2026. I've never seen anybody use YYYY-DD-MM before. When I saw this article I read it as a September 7th update. Shouldn't it be YYYY-MM-DD, like 2026.07.09?
    • This innovation could solve Global Warming and change refrigerators forever by Sayan Sen Image by Tuan Vy via Pexels Researchers at the U.S. Department of Energy’s Lawrence Berkeley National Laboratory (Berkeley Lab) developed a new way of heating and cooling that used electrically charged atoms or molecules, known as ions, to control changes between solid and liquid states. The method, called "ionocaloric cooling," was described in a study published in the journal Science. The idea was based on a familiar example. When salt is spread on roads before a winter storm, it changes the temperature at which ice forms. The new method worked in a similar way by using ions to change the melting point of a material. This created a controlled phase change, which is the process of a material changing between solid and liquid. When the material melted, it absorbed heat from its surroundings. When it became solid again, it released that heat. This allowed heat to be moved from one place to another without using conventional refrigerant gases. The study addressed a long-standing challenge in refrigeration: developing cooling systems that were energy efficient while using refrigerants that had little or no impact on global warming. Most refrigerators and air conditioners use vapor-compression refrigeration, where a refrigerant gas is compressed and expanded in a continuous cycle to absorb heat from one place and release it somewhere else. Many of these systems use hydrofluorocarbons (HFCs), synthetic refrigerant gases with a high global warming potential (GWP), a measure of how much heat a greenhouse gas can trap in the atmosphere compared with carbon dioxide. The ionocaloric system instead used only solid and liquid materials, removing the need for refrigerant gases. “The landscape of refrigerants is an unsolved problem: No one has successfully developed an alternative solution that makes stuff cold, works efficiently, is safe, and doesn’t hurt the environment,” said Drew Lilley, a graduate research assistant at Berkeley Lab and PhD candidate at the University of California, Berkeley, who led the study. “We think the ionocaloric cycle has the potential to meet all those goals if realized appropriately.” Heating and cooling accounted for more than half of the energy used in homes, making improvements in this area important for reducing energy use and greenhouse gas emissions. Replacing current refrigerants was also part of international climate efforts, including the Kigali Amendment, which was accepted by 145 parties, including the United States in October 2022. Under the agreement, countries committed to reducing the production and consumption of HFCs by at least 80% over the next 25 years. Ionocaloric cooling was one of several caloric cooling technologies under development. These systems worked by making materials absorb or release heat when exposed to an external force. Some used magnetic fields, while others used electric fields. However, these approaches often required relatively strong applied fields while producing smaller temperature changes and lower efficiency. According to the researchers, ionocaloric cooling could produce larger temperature and entropy changes using much lower applied field strengths. In thermodynamics, entropy describes how energy is distributed within a system and plays an important role in how heat moves. Because the working material became a liquid during the process, it could also be pumped through a system, making it easier to transfer heat than in many solid-state cooling technologies. Lilley and Ravi Prasher, a research affiliate in Berkeley Lab’s Energy Technologies Area and adjunct professor of mechanical engineering at the University of California, Berkeley, developed the theory behind the ionocaloric cycle. Their calculations suggested that the method could match or even exceed the efficiency of conventional refrigerant-based cooling systems. To test the concept, the researchers built an experimental system based on an ionocaloric Stirling refrigeration cycle, a version of the Stirling thermodynamic cycle adapted to move heat using ion-driven phase changes instead of conventional refrigerants. The system used a sodium-iodine salt together with ethylene carbonate, an organic solvent commonly used in lithium-ion batteries. Applying a small electrical current moved ions through the system, changing the material's melting point. As the material melted, it absorbed heat. When the ions were removed, the material solidified and released the stored heat. The researchers reported that the experimental system achieved a coefficient of performance (COP) equal to about 30% of the theoretical Carnot limit, which represents the highest possible efficiency any cooling system can achieve under ideal conditions. It also produced an adiabatic temperature change, meaning the material's temperature changed without gaining or losing heat to its surroundings, of up to 25 degrees Celsius using an applied voltage of about 0.22 volts. According to the study, this temperature change was larger than those demonstrated by other caloric cooling technologies while operating at a comparatively low voltage. “There’s potential to have refrigerants that are not just GWP [global warming potential]-zero, but GWP-negative,” Lilley said. “Using a material like ethylene carbonate could actually be carbon-negative, because you produce it by using carbon dioxide as an input. This could give us a place to use CO2 from carbon capture.” Prasher said the team was trying to balance environmental impact, energy efficiency and equipment costs. “There are three things we’re trying to balance: the GWP of the refrigerant, energy efficiency, and the cost of the equipment itself,” Prasher said. “From the first try, our data looks very promising on all three of these aspects.” While most caloric technologies were discussed for cooling, the researchers said they could also be used for applications such as water heating and industrial heating. The team was continuing to develop prototypes to test different materials, improve the system's efficiency and temperature range, and determine whether the technology could be scaled up for practical use. “We have this brand-new thermodynamic cycle and framework that brings together elements from different fields, and we’ve shown that it can work,” Prasher said. “Now, it’s time for experimentation to test different combinations of materials and techniques to meet the engineering challenges.” Source: Berkeley Lab, Science This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • Microsoft has several different customer groups. Services (like Azure), Office, dev tools, Windows server and Windows client which itself breaks into three groups: enterprise, education and consumer. The consumer product is one of the least profitable sections and is mainly used to get consumers to buy the other groups like Office and Services, so MSFT tends to focus on staying relevant more than being feature complete or even bug free. That would be tolerable, but MSFT takes the literal opposite approach to Apple who waits for a technology to mature enough that it's about to take off, tweaks it a little then releases a "magic" version and comes off looking like an innovative company. Instead, MSFT tends to look for the "next big thing" and gets on the bandwagon as soon as possible - usually long before the technology is ready for consumer products - and usually at 110%. Most of the time, it turns out that "next big thing" ends up being a niche product (Win 10 was 3D everything, 3D printing, modelling and "XR" for visualisation) or just wrong (Win 8 and "tablets are the future") forcing MSFT to backpedal after blowing tons of money. Win 11 was "The Web as the OS", AI (and weirdly "AI as the OS") and ARM/Copilot+ PCs, all of which have turned out to be mistakes or flops to some degree or entirely.
  • Recent Achievements

    • Reacting Well
      Gideon Waxfarb earned a badge
      Reacting Well
    • First Post
      NovaEdgeX earned a badge
      First Post
    • One Month Later
      pahariyaseo earned a badge
      One Month Later
    • Week One Done
      pahariyaseo earned a badge
      Week One Done
    • Week One Done
      hadiaali45 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      427
    2. 2
      PsYcHoKiLLa
      144
    3. 3
      Nick H.
      90
    4. 4
      Steven P.
      81
    5. 5
      +Edouard
      80
  • Tell a friend

    Love Neowin? Tell a friend!