If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
I'm running Win7 64bit and have an Optional Update in Windows Updates -
KB2999226. Seems to have something to do with Win10 compatibility or something. Is this update really necessary on my system? Thanks for any insights. charliec |
Ads |
#2
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
On Thu, 17 Sep 2015 12:08:32 -0700, wrote:
I'm running Win7 64bit and have an Optional Update in Windows Updates - KB2999226. Seems to have something to do with Win10 compatibility or something. Is this update really necessary on my system? Thanks for any insights. charliec I have the same version and based on what I read he https://support.microsoft.com/en-us/kb/2999226 I decided to hide it. DC |
#3
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
|
#4
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
On Thu, 17 Sep 2015 13:08:22 -0700, "David E. Ross" wrote:
On 9/17/2015 12:08 PM, wrote: I'm running Win7 64bit and have an Optional Update in Windows Updates - KB2999226. Seems to have something to do with Win10 compatibility or something. Is this update really necessary on my system? Thanks for any insights. charliec As Stomin' Norman stated, this is to run Windows 10 desktop apps on Windows 7. Since I do not run any Windows desktop apps for any Windows versions, I did not install this. Instead, I marked it Hidden. Thanks all for the replies - I already have it Hidden and will leave it there for now. Again, thanks all! charliec |
#5
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
wrote:
I'm running Win7 64bit and have an Optional Update in Windows Updates - KB2999226. Seems to have something to do with Win10 compatibility or something. Is this update really necessary on my system? Thanks for any insights. charliec "Update for Universal C RunTime in Windows" https://support.microsoft.com/en-us/kb/2999226 That would be the equivalent of msvcrt.dll in an older copy of Windows. The C runtime library is the base library used/needed by a C program you write and compile. I expect in this case, it probably supports more than C, as for Microsoft, C is deprecated. If a program you buy in the future complains it cannot find "Api-ms-win-crt..." now you know why. When you run a Win10 style application on your Win7 box. This might be one (of many) dependencies. Who knows how much more gratuitous back porting these jokers are going to do. "If you won't take our Win10, we'll make your Win7 into a Win10 the hard way - one file at a time" :-) :-) http://gs.statcounter.com/#os-ww-monthly-201408-201509 Paul |
#6
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
|
#7
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
charliec wrote:
KB2999226 https://support.microsoft.com/en-us/kb/2999226 Just another version of Microsoft C run-time. Most C-coded programs do not roll up all libs they call into the .exe as that would enlarge the size of that file. Since (the assumption) the C run-time libs are already on the Windows hosts, the program author can reduce the size of his .exe file. Each version of the C run-time deprecates some old functions while added new ones. A Win10-enabled C run-time probably has some new functions which may not be solely for use under Win10. If a program author used some of the new functions but all you had was the prior version of the CRT then his program won't run correctly. Think of like this: when you installed Windows, it came with the minimal version of DirectX with that distribution of Windows. Eventually games wanted to use features in a later version of DirectX that became available as the minimal DX version in that new OS. To let the games run on prior versions of Windows meant distributing the newer DX on the older Windows. That way, you didn't have to move to the new version of the OS, just get a newer version of DX on the older OS. No C run-time, any version, is required UNLESS you have a program that needs it. Similarly, you don't need any versions of .Net Framework unless you have a program that requires that programming framework. You may not want Win10 CRT or .Net v4 on your computer now but you may later want to use an app that requires one or both of those libs. Sometimes installers include the run-times on which the program depends but that bloat the size of the installer. For those that do not bundle the run-times with their program, and if you don't have the proper version of the run-time or framework, you might now know why the program you just installed won't load, crashes, or misbehaves. You might think now that you don't want any apps designed for Windows 10 to run on your prior Windows platform. Later you might because the program not only brings wanted features on Windows 10 but is backward compatible with Win7/8. A program written to run on Windows 10 doesn't mandate inheritence of the incarnate evil of Windows 10 when ran in an earlier version of Windows. Apps are apps. What they do depends on how they were coded. Microsoft could've left the situation that the Win10 CRT was available only on Windows 10, so any programs written that require that particular CRT version can only run on Windows 10. Until proven through use, and known only to programmers, it is possible some features on the Win10 CRT can be used on Win7/8 and some cannot which means Win10 apps written using Win10 CRT will be crippled when ran back on Win7/8. You could hide this update until it becomes known to programmers if something of the Win10 CRT installed on Win7/8 results in deficiencies that are absent when using Win10 CRT install on Win10. Until you have an app that you want to use that mandates the later version (Win10) of the C run-time, there is no point in installing it now on a prior version of Windows. However, as noted, sometime later you might want to use that Win10 app that says it runs on Wn7/8 but it won't until you install the Win10 CRT. You probably have several versions of the VB and C run-times installed on your computer. Some old versions are probably never called by any app you use now or will later. But no one gets their knickers in a knot in leaving around the old unused versions that occupy little disk space. I don't see this as an evil or covert update that tries to lure users to Windows 10 or devolves Win7/8 into adware platforms for Windows 10. Unless further proof is provided, it's just another but later version of the C run-time. |
#8
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
On Fri, 18 Sep 2015 04:15:17 -0500, VanguardLH wrote:
Just another version of Microsoft C run-time. Most C-coded programs do not roll up all libs they call into the .exe as that would enlarge the size of that file. Since (the assumption) the C run-time libs are already on the Windows hosts, the program author can reduce the size of his .exe file. I have only one data point, but it goes against what you said. I work for a company whose software depends on MSVC++ runtimes, and it includes them in the installer. Testing in clean Windows systems from Windows XP to Server 2012, I pretty much always see those runtimes getting installed, which wouldn't happen if they were already there. -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#9
|
|||
|
|||
Windows 7 Optional Update - KB2999226?
Stan Brown wrote:
VanguardLH wrote: Just another version of Microsoft C run-time. Most C-coded programs do not roll up all libs they call into the .exe as that would enlarge the size of that file. Since (the assumption) the C run-time libs are already on the Windows hosts, the program author can reduce the size of his .exe file. I have only one data point, but it goes against what you said. I work for a company whose software depends on MSVC++ runtimes, and it includes them in the installer. Testing in clean Windows systems from Windows XP to Server 2012, I pretty much always see those runtimes getting installed, which wouldn't happen if they were already there. I thought I said that. "Sometimes installers include the run-times on which the program depends but that bloats the size of the installer. For those that do not bundle the run-times with their program, ...". End-user programs, from my experience, usually do not include the run-time upon which the program is dependent. Enterprise software targets customers with bigger budgets so their install package includes all run-times, ancilliary software, and any other software the program might need in special scenarios. When a customer is buying an $80K program, you don't skimp on the install package. If there is no concern over download bandwidth or in file server space then the installer might include the run-times. If file server space is limited, especially when hosting the installer elsewhere (e.g., download site), or there is a concern about bandwidth (how big, how long the download takes, not all download sites support resume), then the installer might include the run-time. In the latter case, it is assumed that you already have the required run-time version, or already have a later version that is usable, or the installer may offer to retrieve the run-times for you and start their installs, or the site tells you about having to download other software to get the program to function. KB2999226 says it delivers the "universal" C run-time. Universal? This article had a link to another about the Win10 SDK. Instead of mandating a user be using Windows 10 as a minimal platform to run an app that was written to run under Windows 10, it looks like the Win10 CRT and Win10 SDK are designed not only to allow running a "universal" app on desktops, notebooks, pads, and mobile devices but also run them under Windows 7, 8, and 10. An app that can only run under Windows 10 would have a limited audience compared to the same app that can run on all those hardware platforms under Windows 7, 8, and 10. However, to do that means the support framework (e.g., run-times) must be available for those operating systems. Windows 7 and 8 users are probably leery of anything saying it is for Windows 10, and rightly so considering the so-called updates that are not for Windows 7/8 but are for migration to or lures for Windows 10 or to convert Win7/8 setups to adware platforms for Win10. Win7/8 users are getting tired of the Win10 bait updates. Time might disprove my assumption but it looks like Microsoft is trying to widen the audience for Win10 apps so they can run back on Win7/8 by not restricting a version of CRT to Windows 10, or later, but allowing distribution and use of the newer CRT on older versions of Windows. While this looks noble of Microsoft, this does have a marketing ploy as another lure as to why Win7/8 users should be using Win10. As I mentioned, I hope the Win10 version of the CRT doesn't cripple itself when used under Win 7/8; else, this would be like freeware that is a crippled version of the full program. If freeware is so crippled as to be merely a demo of the full program then that freeware is really lureware. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|