locked
Windows 10 systems stop updating status reports after in-place upgrades RRS feed

  • Question

  • 10 workstations had an in-place upgrade from 1511 to 1703 last night.

    The upgrades were all successful and they are all online and contacting WSUS because the "last contact time" is within the last couple of hours for all of them.  However, the "last status report" time has not updated since yesterday.  So, they all show as still needing updates  applicable to Windows 10 1511.

    Systems that were not upgraded are reporting normally.  Only the systems that were updated last night have this issue.

    I ran the GP Results wizard on one of them and the check for updates interval is set as every 2 hours.

    What needs to be done to get systems to report to WSUS properly after an OS upgrade?



    • Edited by Kalimanne Friday, September 15, 2017 3:22 PM
    Friday, September 15, 2017 3:20 PM

All replies

  • WSUS requires patience. Wait for 24-72 hours of an ONLINE connected system, or a week for one that goes offline like a laptop.

    You can force a client to do it.

    wuauclt /detectnow

    Wait about 8 minutes

    wuauclt /reportnow (or wait 20 min after detectnow has finished)


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Sunday, September 17, 2017 4:05 AM
  • The issue is that these systems are all desktops that are online 24/7 and are configured by GPO to check in every 2 hours.  All the other systems other than the ones that had the in-place upgrade are checking in and updating status reports as expected.  

    I also read elsewhere that the wuauclt reportnow commands are for older operating systems and don't work for Windows 10.

    Sunday, September 17, 2017 4:21 AM
  • Am 17.09.2017 schrieb Kalimanne:

    I also read elsewhere that the wuauclt reportnow commands are for older operating systems and don't work for Windows 10.

    Where you did read this? Microsoft.com?

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Sunday, September 17, 2017 9:44 AM
  • Hello,

    The wuauclt.exe /detectnow command has been removed and is no longer supported in Windows 10. Instead, you should run these PowerShell commands:

    $AutoUpdates = New-Object -ComObject "Microsoft.Update.AutoUpdate"
    $AutoUpdates.DetectNow()

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 18, 2017 6:49 AM
  • Am 18.09.2017 schrieb Andy Liu50:

    The wuauclt.exe /detectnow command has been removed and is no longer supported in Windows 10. Instead, you should run these PowerShell commands:$AutoUpdates = New-Object -ComObject "Microsoft.Update.AutoUpdate"
    $AutoUpdates.DetectNow()

    Is there any documentation from MSFT? Thanks.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Monday, September 18, 2017 3:16 PM
  • They did start reporting after waiting over the weekend, but there is something about doing the in-place upgrades that initially causes these systems to lose the 2 hour interval that is set in the Windows Update policies.
    Monday, September 18, 2017 7:28 PM
  • Hello,

    Have you ever configured the Defer Windows Updates group policies? If configured, could you please disable the two policies first, and then to see if the issue occurs again?

    @Winfried https://docs.microsoft.com/en-us/windows-server/get-started/deprecated-features

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, September 27, 2017 9:29 AM