My windows 7 Update says 2 important updates are available but when i click
install updates it doesn't install the updates for many hours ! So how to fix this problem ? Should i install those two updates or just leave it as it is ?
(Note:Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983) is already installed successfully and many other security updates)
2 important updates that doesn't install:
Microsoft .NET Framework 4.6.1 for Windows 7 for x64 (KB3102433)
Security Update for Windows 7 for x64-based Systems (KB3110329)
Try downloading the updates, disconnecting the PC from the internet and then running the update. See here: https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates for a more detailed guide on the problems with Windows Update
Related
I have problem on Windows Server 2019, all application which use .Net cannot be started. I have 4.8 version with all windows update. But I get this error. I tried reinstall, use fix tool for .NetFramework but i cannot fix .NetFramework
enter image description here
We just found this solution. (https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/windows-server-2019-and-net-4-8/m-p/2660319)
I ran into this issue after the Windows Update, Cumulative Update for .NET Framework (KB5006765), was installed on a Windows Server 2019 that also had Azure AD Connect installed. Apparently, a bunch of .NET registry items where deleted. Server Manager and any software built on .NET was not working...throwing this error:
This application requires one of the following versions of the .NET Framework: v4.0.30319
Do you want to install this .NET Framework version now?
DSIM and SFC repairs did not work, nor did rolling back the Windows Update.
Found some insight here:
https://www.bleepingcomputer.com/forums/t/758800/net-48-kills-server-2019/
Ended up having to import these registry items from a working system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs\Default]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"AspNetEnforceViewStateMac"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.1,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.2,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0.3,Profile=Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.5.3]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.6.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.7.2]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\Client]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\SKUs\Default
We are using 'CentOS Linux release 7.9.2009 (Core)' for production servers. But it seems that Redhat stopped Centos 7 full updates from November 2020 onwards. We are in confusion do we need to upgrade to CentOS 8 or Centos Stream?, As per Centos / wiki official docs. They were providing full/maintenance support for Centos 8 Stream still 2024. Is this Centos 8 Steam version is stable or can we continue with Centos 7 maintenance version?
Reference URLS :
https://wiki.centos.org/About/Product,
https://en.wikipedia.org/wiki/CentOS#CentOS_version_7
In my career i have seen prod servers even running on Solaris 11 which was released 10 years ago and has no support now.
This usually depends, whether the underlying dependencies required by your application change/requires to be updated frequently or not,
If yes - Go with supported version.( which will also run out of support :D )
If No - Stay where you are. ( Best choice Mostly )
I'm trying to get a legacy Powerbuilder 8 application to work in a Windows 10 environment. The application has not been installed from any installation package, I simply open it from a network share containing all the necessary files. It works this way in Windows 7 systems. In Windows 10 the app opens fine, but connecting to database fails with error message:
999: DBMS MSS is not supported in your current installation.
Neither Windows 7 nor Windows 10 workstations have any specific database access drivers installed.
My development environment has Windows 10 and there connection to the database works ok. The database server is installed locally in the dev environment, though.
We had a problem with Powerbuilder 8.4 and 0racle 10 and 11. With Windows 10 patch 1803. When we copied files to local drive it worked. We were getting strange data base error. It had to do with smb version 1. June 30 2018 Windows 10 solved the problems. If your still having problem this may be worth a shot.
I want to install Security and Quality Rollup updates for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2 (KB 4338419) on my PC (Windows Server 2012 R2).
I had a look on it and I saw that I need like a prerequisite Windows Server 2012 R2 Update (KB2919355). On that one I see that I need more stuffs like: KB2919442. I tried from windows Update to have the last updates available. After all the updates was installed I took a look and notice that I have (KB 4338419) and (KB2919355) but I don't have KB2919442.
Is that a problem? If I try to install it manually I get "The update is not applicable to your computer."
From http://support.microsoft.com/kb/2919355/EN-US:
When you install this update (2919355) from Windows Update, updates
2932046, 2937592, 2938439, 2934018, and 2959977 are included in the
installation.
Prerequisites:
To apply this update, you must have the following update installed on
Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2:
2919442 A servicing stack update is available for Windows RT 8.1,
Windows 8.1, and Windows Server 2012 R2: March 2014
Q: Is that a problem? If I try to install it manually I get "The update is not applicable to your computer."
You need not worry about KB2919442 as that was a prerequisite for KB2919355, which is already installed on your server. You can't install the old update now as you already have the latest updates.
I am working with a client that is running Filemaker Server 5 in a workgroup environment and is now upgrading to a true client server network running either MS windows server 2008 or 2012. Will Filemaker Server 5 run in the new network environment. They do not want to upgrade Filemaker. Any help would be greatly appreciated
Have a look at this:
FileMaker Server operating system requirements - all versions
Windows 2008 does not appear on the list until FileMaker 10. Windows 2012 only supported only with FileMaker 13.
This is an official supported version chart, so you still can try and install it. I am sure, there is a compatibility mode which will let you run it. If you have any problem, you will not be able to get any support from FileMaker.
If updating FileMaker is such an issue, you might be better of running a VM on the same server with an older OS and serve it from there.
You will probably have a similar problem with clients' installs when their workstations are upgraded. FileMaker 15 is around 15 years old.
You should also consider that the filemaker 5 / 6 clients will not install on a new OSX OS Version - I'm not sure about Windows, that should be tested before moving forward if that is a requirement.
All new versions of Filemaker will convert Filemaker 5 files to a new format, however it's a big change and the scripting and layouts need to be checked after conversion. Filemaker 5 is 14+ years old and support stopped around 10 years ago which explains the compatibility issues.