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.

  On 10/01/2014 at 14:56, Frank B. said:

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

  On 10/01/2014 at 22:19, snaphat (Myles Landwehr) said:

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.

  On 11/01/2014 at 07:21, francescob said:

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.

  On 11/01/2014 at 08:20, snaphat (Myles Landwehr) said:

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.

  On 11/01/2014 at 08:45, francescob said:

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)

  On 11/01/2014 at 09:38, snaphat (Myles Landwehr) said:

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.

 

  On 11/01/2014 at 09:38, snaphat (Myles Landwehr) said:

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.

 

  On 11/01/2014 at 10:12, JaykeBird said:

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).

 

  On 11/01/2014 at 10:12, JaykeBird said:

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?

  On 11/01/2014 at 17:14, francescob said:

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

  On 11/01/2014 at 18:12, snaphat (Myles Landwehr) said:

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.

  On 11/01/2014 at 18:12, snaphat (Myles Landwehr) said:

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.

  On 12/01/2014 at 01:15, francescob said:

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?

  On 12/01/2014 at 01:18, snaphat (Myles Landwehr) said:

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

    • Oh wow, a patch for an Unreal game to improve performance? We'll see...
    • Get this massive 4TB WD_BLACK SN7100 SSD at a new all-time low price by Taras Buria Xbox owners recently received a new storage upgrade option, which allows them to equip the Xbox Series X|S with 4TB of extra space. That card, however, has an eye-watering price tag—nearly as much as the 1TB Xbox Series S. On the PC side, though, things are much better. Right now, if you need a 4TB SSD without selling a kidney, you can get the WD_BLACK SN7100 PCIe Gen4 SSD. It is now available on Amazon at a new all-time low price after a 16% discount (nearly half the cost of the new 4TB Xbox Storage Expansion Card). The SN7100 is a fast, reliable, and, more importantly, affordable Gen4 solid-state drive. Its speeds are rated up to 7,000MB/s sequential read and 6,700MB/s sequential write, while random input-output speeds are rated at 900K IOPS read and 1,350K IOPS write. These specs are not record-breaking, but they are fast enough for modern gaming (DirectStorage is supported), fast loading times in games and apps, and quick file transfer. The WD_BLACK SN7100 has a limited five-year warranty and endurance rating up to 2,400 TBW. You can monitor the health of your drive in the WD_Black Dashboard app on Windows. As for compatibility, you can use the SN7100 in any PC that accommodates M.2 2280 PCIe Gen4 drives, including PlayStation 5. It is compatible with PCIe Gen3 systems, but the maximum speeds will be limited. 4TB WD_BLACK SN7100 PCIe Gen4 Solid-State Drive - $249.99 | 16% off on Amazon US This Amazon deal is US-specific and not available in other regions unless specified. If you don't like it or want to look at more options, check out the Amazon US deals page here. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
    • Snagit 2025.2.0 by Razvan Serea Snagit is the most complete screen capture utility available. Showing someone exactly what you see on your screen is sometimes the quickest and clearest way to communicate. With Snagit, you can select anything on your screen – an area, image, article, Web page, or error message – and capture it. Then, save the screen capture to a file, send it to Snagit​'s editor to add professional effects, share it by e-mail, or drop it into PowerPoint®, Word®, or another favorite application. Capture and share images, text or video from your PC. Create beautiful presentations, flawless documentation and quickly save online content. The latest version of Snagit offers a totally new interface and workflow - making SnagIt easier for beginners to use, while still providing maximum convenience and flexibility for the screen capture experts. Snagit 2025.2.0 changelog: Edit Images from Camtasia Snagit can now be used to seamlessly edit images from Camtasia. Requires Camtasia version 2025.2.0 or later. In the Camtasia Media Bin, right-click an image and select the Edit in Snagit option. In Snagit, make your edits. When finished, click Send in the "Send changes to Camtasia" notification to replace the image on your Camtasia timeline. Step Capture Improved the Step Capture template to accommodate longer auto-populated step text. Annotations such as Callout or Arrow tool objects now anchor to and move with sections as sections are added to, reordered, or deleted from templates. Subscription Software Updated the Account dropdown to open automatically when new subscription related messages are present. Performance Improvements Improved the startup time for Snagit Capture application. Updates for IT Administrators Updated BouncyCastle.Cryptography package to address CVE-2024-29857 and CVE-2024-30172. Removed dependency on Xceed Zip. Updated LeadTools DLLs. Fixed an issue where Snagit might not recognize offline subscription activation. Fixed an issue where the video recording toolbar could be hidden from users when using Snagit in virtual environments or with remote desktop applications. Bug Fixes Fixed an issue where using Step Capture with the Share destination set to File in the Capture Window could result in data loss. Fixed a crash that could occur when capturing on some HDR monitors. Fixed an issue where the cursor object in a capture might include some of the background image in certain situations. Fixed an issue with the Box share destination to use the default browser for authentication. Fixed an issue where the Blur tool Color property could show when the blur or pixelate Type was selected. Fixed an issue where the privacy policy link in Snagit's installer might not open in the expected language. (PONRPD) Download: Snagit 64-bit | 419.0 MB (Shareware) Links: SnagIt Home Page | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Markdown's creator weighs in on rumored Apple Notes export feature by David Uzondu The rumor mill is churning as we draw closer to WWDC2025, and one of the interesting developments being discussed is a report from 9To5Mac that claimed Apple Notes in iOS 19 iOS 26, will finally get Markdown export capabilities. This caught the attention of many, including the person who actually invented Markdown. John Gruber, the creator of Markdown, shared his thoughts on this potential new feature on his weblog. For those who don't know, Markdown, which Gruber developed back in 2004 with significant input from Aaron Swartz (RIP!), is a lightweight markup language designed for creating formatted text using a plain text editor. Its main advantage is that it is easy to read and easy to write. When the news first broke, some interpretations suggested Apple Notes would gain full Markdown support, transforming it into an application where users could directly type and see Markdown syntax, much like how specialized editors like Obsidian operate. These tools are intended for users to work directly within the Markdown framework for all their note-taking. Gruber himself indicated that he does not believe Apple Notes should become a full-fledged "Markdown editor," even as an option. He stated that such a change would be a "huge mistake." His reasoning is rooted in his original vision for Markdown and his view of Apple Notes' purpose. He reiterated that he initially designed Markdown as a "text-to-HTML conversion tool for web writers" and for contexts requiring plain text file storage. He feels Apple Notes serves a different, valuable role with its current WYSIWYG (What You See Is What You Get) rich text editing. This interface, he argues, is excellent for quickly capturing thoughts, particularly on an iPhone, and aligns with the Macintosh philosophy of user-friendliness. He pointed out that creating a syntactically incorrect markdown is trivial, whereas a malformed note should not be possible with Apple Notes. Despite his reservations about a complete Markdown overhaul for the editing experience, Gruber finds the prospect of exporting notes in Markdown format very appealing. He wrote that this specific capability "sounds awesome." He pointed out, quite rightly, that Apple Notes' current export functions are rather limited, primarily offering PDF and Pages document formats. Adding Markdown export would provide a much more flexible way for users, especially those in the "niche" he identifies with, to move their content out of Notes and into other applications. Gruber did express curiosity about how Apple might handle images embedded in notes during a Markdown export, as image handling can be a tricky aspect of Markdown.
    • What? Every single app I've installed from the Microsoft Store comes from its intended developer and works perfectly fine. What apps do you install?
  • Recent Achievements

    • Week One Done
      jfam earned a badge
      Week One Done
    • First Post
      survivor303 earned a badge
      First Post
    • Week One Done
      CHUNWEI earned a badge
      Week One Done
    • One Year In
      survivor303 earned a badge
      One Year In
    • Week One Done
      jbatch earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +FloatingFatMan
      182
    3. 3
      snowy owl
      181
    4. 4
      ATLien_0
      176
    5. 5
      Xenon
      139
  • Tell a friend

    Love Neowin? Tell a friend!