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

    • Microsoft's new Exchange Message Trace: What admins need to know before September by Paul Hill Microsoft has just announced the general availability of the new Message Trace in the Exchange admin center (EAC) in Exchange Online for its worldwide (WW) customers. The Redmond giant said that it’ll begin rolling it out in mid-June and complete the rollout in July. Message Trace in the Exchange Admin Center for Exchange Online is a tool that lets admins trace which path emails took as they traveled through the Microsoft 365 organization. It lets admins see if emails were received, rejected, or deferred. It is helpful for troubleshooting mail flow issues and validating policy changes. To get started with the new Message Trace, admins can access it by going to the Exchange admin center > Mail flow > Message Trace. While the Windows-maker has received positive feedback during the Public Preview, you can still provide your thoughts through Exchange admin center > Give Feedback. In addition, Microsoft will continue to maintain the old Message Trace user experience in Exchange admin center and cmdlets for several months to ease the transition, however, they will be deprecated for WW customers starting from September 1. The Reporting Webservice support for Message Trace data will also begin deprecating on this date. A side note to mention here is that this timeline only applies to the WW environment and doesn’t affect GCC, GCC-High, DOD, or other sovereign clouds. More information about the switch over for those will be provided in the second half of the year. Who it affects, and how These changes need to be noted by Exchange Online administrators and IT professionals as those are the people who will be directly affected. Specifically, it will affect anyone managing mail flow and troubleshooting email delivery in Exchange Online. Those who are affected will have to get switched over to the new Message Trace before Microsoft starts deprecating features in several months time. Admins will want to act promptly to avoid any unforeseen issues that could arise. Another detail that admins should be aware of is that scripts that rely on the older “Get-MessageTrace” or “Get-MessageTraceDetail” cmdlets will break on September 1. To address this, admins will need to update their scripts to use the new “Get-MessageTraceV2” and the “Get-MessageTraceDetailV2” cmdlets. Finally, any admins out there using the Reporting Webservice for Message Trace data will also need to make a change. They will need to shift to the new Message Trace PowerShell cmdlets. Why it’s happening Microsoft has been working on a new Message Trace experience, incorporating feedback from the Public Preview phase, to improve its design and performance. The switch gives Microsoft the opportunity to standardize and modernize admin interfaces and the underlying technologies. What to watch for While September 1 may seem like a long way away, fixing any issues, such as scripts due to deprecations, could take some time. Any admins managing the affected items need to ensure they deal with affected components in a timely manner. In terms of documentation, Microsoft has so far only released the Public Preview document which highlights the changes between the old and new versions. Microsoft says that it will publish cmdlet documentation for the new Message Trace cmdlets by the time of the general availability, so admins should look out for that.
    • Microsoft PC Manager 3.17.2.0 (Offline Installer) by Razvan Serea With Microsoft PC Manager, users can easily perform basic computer maintenance and enhance the speed of their devices with just one click. This app offers a range of features, including disk cleanup, startup app management, virus scanning, Windows Update checks, process monitoring, and storage management. Microsoft PC Manager key features: Storage Manager- easily uninstall infrequently used apps, manage large files, perform a cleanup, and set up Storage Sense to automatically clear temporary files. Health Checkup feature -scans for potential problems, viruses, and startup programs to turn off. It helps you identify unnecessary items to remove, optimizing your system's performance. Pop-up Management - block pop-up windows from appearing in apps. Windows Update - scans your system for any pending updates. Startup Apps - enable or disable startup apps on your PC, allowing you to optimize your system's startup performance. Browser Protection - rest assured that harmful programs cannot alter your default browser. Also enables you to change your default browser. Process Management - allows you to conveniently terminate any active process, ensuring optimal system performance and resource utilization. Anti-virus protection - Fully integrated with Windows Security. Safeguard your PC anytime. Quick Steps: Download Microsoft PC Manager Offline Installer (APPX/MSIX) with Adguard Adguard serves as a third-party online service, offering a user-friendly method for directly downloading appx, appxbundle, and msixbundle files from the Microsoft Store. Official download links will be generated for both the app's various versions and its dependency packages. How to download Microsoft PC Manager Offline Installer (APPX/MSIX) 1. Initially, you must find the app URL within the Microsoft Store. Access the Microsoft Store via your browser and search for "Microsoft PC Manager". Once located, copy the app URL, which includes the product ID, either from the address bar or from the provided link below. https://apps.microsoft.com/detail/9PM860492SZD 2. Now paste the app URL into the designated area, then click the check mark button to produce a direct download link. 3. To download, right-click the relevant link and select “Save link as…” from your browser's menu. Occasionally, Microsoft Edge may flag the download as insecure. In such cases, consider utilizing alternative browsers such as Google Chrome or Firefox to successfully complete the download. Microsoft PC Manager is a completely free tool optimized exclusively for use on Windows 10 (version 1809 or newer) and Windows 11. Download: Microsoft PC Manager 3.17.2.0 | from Microsoft Store View: Microsoft PC Manager Home Page Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Vivaldi, spiritual fork of the original opera browser, highly configurable 
    • You could have moved her to Apple. Would have been the same ending. For the basic stuff it's fine, I agree.
    • iFixit explains why it is cutting the repairability score of the Nintendo Switch by half by David Uzondu With less than three days till the official release of the Nintendo Switch 2, iFixit just announced it is chopping the original Switch's repairability score clean in half, taking it from an 8 out of 10 all the way down to a 4. Now, the actual console from 2017 has not changed a bit, but iFixit says its way of looking at repair and what is even possible in handheld gaming has come a long way in eight years. The company figured that with the Switch 2 about to drop, people would want a proper way to compare the old with the new. Back when the Switch first came out, it was a weird one to score because it was part console, part handheld. iFixit now feels it has a better handle on things, and since Nintendo itself says most people play the Switch undocked, the device is getting judged harder as a portable machine. The iFixit Repairability Scoring Rubic So, what are the big complaints making iFixit take an axe to the score? Well, that glued-in battery is still incredibly difficult to remove, and the only way to charge the thing is through a port soldered right onto the main circuit board, which is always a recipe for repair nightmares. On top of that, Nintendo has never bothered to sell official replacement parts for the original Switch or even give out official repair guides. You cannot just ignore issues like that when you are talking about how easy something is to fix. Even finding one of the specific types of thermal goop you need for many fixes inside the console has been a pain. And while everyone knows about the Joy-Con drift, iFixit is clear its score does not hit for bad durability, but seeing so many busted joysticks has made how easy they are to fix a bigger deal in its scoring lately. This is not the first time iFixit has had to go back and change a score based on new information or a change in how it sees things, like in 2023 when it cut the iPhone 14's repairability score because Apple started using software to link almost every part to a specific phone, making independent repairs a massive pain even if the phone was physically easier to open. iFixit still gives Nintendo credit for the plug-and-play joysticks (even if they drift), storage you can replace and add to, and an inside layout that is mostly simple. But those good points just do not count for as much when you compare the Switch to what is out there now and how much easier other companies like ASUS with the ROG Ally and Lenovo with the Legion Go, are making repairs. iFixit is hoping Nintendo learned a few things for the Switch 2. Plus, there is a Right to Repair law in New York that kicked in for gadgets made after July 1, 2023. That law might just force Nintendo to sell parts and share repair info for the new console, at least for things like batteries and screens. If Nintendo starts selling parts and guides for the original Switch while people are still buying it, iFixit says it will happily look at the score again.
  • Recent Achievements

    • Week One Done
      Leonard grant earned a badge
      Week One Done
    • One Month Later
      portacnb1 earned a badge
      One Month Later
    • Week One Done
      portacnb1 earned a badge
      Week One Done
    • First Post
      m10d earned a badge
      First Post
    • Conversation Starter
      DarkShrunken earned a badge
      Conversation Starter
  • Popular Contributors

    1. 1
      +primortal
      261
    2. 2
      snowy owl
      158
    3. 3
      +FloatingFatMan
      145
    4. 4
      ATLien_0
      140
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!