Forum Discussion

Harman_Thind's avatar
Harman_Thind
Icon for Microsoft rankMicrosoft
Sep 08, 2022

What's New in Windows Autopatch: September Edition

Check out the latest Monthly Blog on 'What's new in Windows Autopatch: September 2022'! This blog highlights the following: Windows Autopatch will create the following enterprise applicatio...
bernathe's avatar
bernathe
Copper Contributor
Sep 14, 2022

Chris_Tulip thanks for the reply. I had opened a ticket with support and they replied that

 

“our Dev team has identified a bug with Autopatch readiness check and fixed it. The service automatically runs these checks once a day so it may take 24 hours for devices to appear in the "Ready' tab.  Feel free to contact us in case of follow-up questions or queries.”

 

It appears to be working now. 

 

Chris_Tulip's avatar
Chris_Tulip
Icon for Microsoft rankMicrosoft
Sep 15, 2022
Great - addresses the issue you were mentioning on the Device Registration page, glad you got it sorted out! My previous comment was regarding your second screenshot on the Release Management page - are you still seeing issues there or did that get addressed int he same ticket?
  • bernathe's avatar
    bernathe
    Copper Contributor
    Sep 15, 2022

    Chris_Tulip - Sorry about that, I missed the reference to the release schedule.  That issue is still outstanding as is the ticket.  The first step was to get systems reporting correctly and now that that is resolved we are moving onto the release schedule invalid date issue.  

     

    I'm quite certain none of the default autopatch policies have been modified (this is a brand new autopatch enablement) and when I review the "Update rings for Windows 10 and later" the last modified date matches the creation date for all.  The "Feature updates for Windows 10 and later (preview)" policies creation and modified do not match but they are all the exact same for all ring groups.

     

    Looking forward to further developments!

     

     

    • bernathe's avatar
      bernathe
      Copper Contributor
      Sep 16, 2022
      The invalid date issue ended up to be a Firefox specific issue. I was using FF for a dev and test tenant for autopatch testing. Switching to Edge or Chrome resolved the Invalid Date display issue.