NetworkNinja Posted February 21, 2019 Posted February 21, 2019 This week I have performed 2 in place upgrades on our domain controllers. DC2 went perfect and everything is working fine however DC1 is not finding any updates to install. I know I should not do in place upgrades but it was our only option at this time. Anyone had this issue before. I have tried several things to get it working but nothing seems to work. Dism Cleanup - Nothing SFC Scan Now - Nothing Windows Update Diagnostic - Found errors and fixed but still not working Deleted the software distribution folder Plenty of restarts. This is a sample from the windows log file. The log has been updating all night. 2019-02-20 20:01:43:974 920 1004 AU ## START ## AU: Install updates2019-02-20 20:01:43:974 920 1004 AU #########2019-02-20 20:01:43:974 920 1004 AU # Initiating scheduled install2019-02-20 20:01:43:974 920 1004 AU WARNING: There are no approved updates to install2019-02-20 20:01:43:974 920 1004 AU # Exit code = 0x8024000C2019-02-20 20:01:43:974 920 1004 AU #########2019-02-20 20:01:43:974 920 1004 AU ## END ## AU: Install updates2019-02-20 20:01:43:974 920 1004 AU #############2019-02-20 20:02:22:632 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:27:975 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:27:975 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:27:991 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:30:194 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:30:460 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:30:460 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:46:585 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:48:445 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:48:445 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:48:445 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:48:742 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:02:48:960 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:02:48:976 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:06:17:174 920 1004 AU AU received policy change subscription event2019-02-20 20:08:17:427 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:08:17:427 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:08:18:396 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:08:18:646 920 1004 Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=22502019-02-20 20:08:18:959 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:08:18:959 920 1004 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x802400372019-02-20 20:11:18:042 920 1004 AU AU received policy change subscription event2019-02-20 20:16:18:831 920 1004 AU AU received policy change subscription event2019-02-20 20:21:19:684 920 1004 AU AU received policy change subscription event2019-02-20 20:26:20:460 920 1004 AU AU received policy change subscription event2019-02-20 20:31:21:218 920 1004 AU AU received policy change subscription event2019-02-20 20:32:48:282 920 9ac IdleTmr Decremented idle timer priority operation counter to 02019-02-20 20:33:09:158 920 cfc IdleTmr Incremented idle timer priority operation counter to 1 - - - Updated - - - Since Last night the only error on the log file is the following - 2019-02-21 07:27:59:687 920 1004 AU AU received policy change subscription event
NetworkNinja Posted February 22, 2019 Author Posted February 22, 2019 Just in case anyone else has this issue i have found a solution that worked for me. Windows update, stuck in ‘Checking updates’ quite long time Check the Windows update agent version, for that go to C:\Windows\System32 Check the ‘wuaueng.dll’ file version. If it the version is either of the following 7.9.9600.17031, 17415, .17729, .17959, .18039, .18094, .18145, then we need to install the patch KB3138615. https://support.microsoft.com/en-in/help/3138615/windows-update-client-for-windows-8.1-and-windows-server-2012-r2-march-2016 We need to Disconnect the server from network and stop the windows update service, before installing the patch 2
Hyakurai Posted October 19, 2019 Posted October 19, 2019 Thank you so much. I'd been stuck on this issue for over a week. How did you figure out that solution? In any case, this is the right answer to issues with WSUS updates on a machine that was upgraded in-place to Windows 2012 R2 where your search for updates hangs indefinitely. I was also seeing the 0x80244010 max roundtrips exceeded errors initially, but once I worked around that by retrying the update search a few times the search would never finish.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now