Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      This week in AI dev tools: Gemini 2.5 Pro and Flash GA, GitHub Copilot Spaces, and more (June 20, 2025)

      June 20, 2025

      Gemini 2.5 Pro and Flash are generally available and Gemini 2.5 Flash-Lite preview is announced

      June 19, 2025

      CSS Cascade Layers Vs. BEM Vs. Utility Classes: Specificity Control

      June 19, 2025

      IBM launches new integration to help unify AI security and governance

      June 18, 2025

      I replaced my Pixel 9 Pro with a $750 Android for a week. Now I’m questioning my loyalty

      June 21, 2025

      Less UFO, more Wall-E: You’ve never seen the best robot vacuum on the market

      June 21, 2025

      ChatGPT can now sum up your meetings – here’s how to use it (and who can)

      June 21, 2025

      One of World of Warcraft’s deadliest entities makes a world-shattering return after nearly 20 years — and he’s city-sized

      June 20, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      Lakeflow: Revolutionizing SCD2 Pipelines with Change Data Capture (CDC)

      June 21, 2025
      Recent

      Lakeflow: Revolutionizing SCD2 Pipelines with Change Data Capture (CDC)

      June 21, 2025

      vitorccs/laravel-csv

      June 21, 2025

      Dr. Axel’s JavaScript flashcards

      June 20, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      Microsoft to Begin Phasing Out Legacy Drivers From Windows Update for Security and Stability

      June 21, 2025
      Recent

      Microsoft to Begin Phasing Out Legacy Drivers From Windows Update for Security and Stability

      June 21, 2025

      Samsung Partners With EA and Xbox to Bring FC 25 to Gaming Hub

      June 21, 2025

      Microsoft may end high-stakes OpenAI talks, and keep the current contract

      June 21, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Operating Systems»Windows 11 24H2 System Restore points now expire after 60 days, Microsoft confirms

    Windows 11 24H2 System Restore points now expire after 60 days, Microsoft confirms

    June 21, 2025

    Microsoft has confirmed that Windows 11 System Restore points will be deleted after 60 days, so you need to be more careful and periodically create restore points. This will give you multiple snapshots, but Windows will still delete the oldest ones once they exceed the retention window (now 60 days on Windows 11 24H2 by default).

    Is it more or less than before? It’s hard to tell, really. Ever since Microsoft released the June 2025 update with a new 60-day policy, I’ve been testing different builds of Windows 11 on multiple PCs from varying OEMs to find out how things were before the update.

    Some of my Windows 11 installations’ System Restore would expire after 10 days, but some would stay for up to 90 days.

    Windows 11 System Restore Point Settings

    Microsoft’s old document on “System Restore” tells us nothing about the existing retention period. Not even a word. But when digging through the older documentation, I found a document for Windows Server titled “SystemRestoreConfig class”, dated December 2020, which appears to confirm a 90-day retention period:

    The time interval for which restore points are preserved, in seconds. When a restore point becomes older than this specified interval, it is deleted. The default age limit is 90 days.

    Since the documentation is from 2020, it’s fair to assume that 90 days is the official System Restore point retention period for Windows 10, Server and older, but after Windows 11’s release in 2021, the retention period has been anywhere between 10 and 90 days (mostly 10 days). Now, it’s changing again for the better.

    In the release notes of the June 2025 update, Microsoft confirmed that it’s locking the Restore Point to 60 days.

    “After installing the June 2025 Windows security update, Windows 11, version 24H2 will retain system restore points for up to 60 days,” Microsoft announced in a support document. “This 60-day limit will also apply to future versions of Windows 11, version 24H2.”

    After installing the update, Windows Latest verified the change to 60 days using the PowerShell command:

    PS C:WINDOWSsystem32> $key = 'HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionSystemRestore'
    >> (Get-ItemProperty -Path $key -Name RPLifeInterval).RPLifeInterval
    5184000

    As you can see, we’re getting a value of 5184000, which translates to 60 days (5184000 ÷ 86,400 seconds).

    In case of Windows 10, I’m seeing 7776000 seconds, which translates to 90 days, and it’s in line with older support documents.

    A 13-year-old support document (now deleted) also notes that Windows’ Restore Point was originally designed to expire after 90 days. That was the case in Windows Vista, Windows 7, and later releases. Also, when your device was running low on storage, Windows would delete all restore points in an attempt to free up disk space. This still seems to be the case.

    How to create a System Restore point in Windows 11

    System Restore has always been the “safety net” that lets you roll Windows back after a bad driver, update or app install. To create one, follow these steps (and I recommend creating one after every few weeks):

    1. Open Windows Start and search for Create a restore point.
    2. This will open the System Protection tab in System Properties.
    3. Under Protection Settings, make sure one of the partitions where you intend to create the backup is “protected.”
    4. Select the partition and click ‘Configure’ to turn on protection.
      Windows 11 System Restore Point Settings
    5. Once done, click Create and follow the on-screen wizard process.
      Confirm your restore point
    6. This will create a System Restore point with an expiry of 60 days.

    How often do you create a System Restore point? Let us know in the comments below.

    The post Windows 11 24H2 System Restore points now expire after 60 days, Microsoft confirms appeared first on Windows Latest

    Source: Read More 

    windows
    Facebook Twitter Reddit Email Copy Link
    Previous ArticleTest hints Microsoft Copilot may offer ChatGPT’s o4-mini-high for free
    Next Article As Windows 10 end of support looms, Microsoft says Windows 11 AI is all you need

    Related Posts

    Operating Systems

    Microsoft to Begin Phasing Out Legacy Drivers From Windows Update for Security and Stability

    June 21, 2025
    Operating Systems

    Microsoft may end high-stakes OpenAI talks, and keep the current contract

    June 21, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    Artificial intelligence enhances air mobility planning

    Artificial Intelligence

    How to create issues and pull requests in record time on GitHub

    News & Updates

    Nite Riot: Minimalism Gets a Wild Side

    News & Updates

    Galene is an easy to deploy videoconference server

    Linux

    Highlights

    CVE-2025-20286 – “Cisco ISE Cloud Credential Exposure Vulnerability”

    June 4, 2025

    CVE ID : CVE-2025-20286

    Published : June 4, 2025, 5:15 p.m. | 2 hours, 21 minutes ago

    Description : A vulnerability in Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI) cloud deployments of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to access sensitive data, execute limited administrative operations, modify system configurations, or disrupt services within the impacted systems.

    This vulnerability exists because credentials are improperly generated when Cisco ISE is being deployed on cloud platforms, resulting in different Cisco ISE deployments sharing the same credentials. These credentials are shared across multiple Cisco ISE deployments as long as the software release and cloud platform are the same. An attacker could exploit this vulnerability by extracting the user credentials from Cisco ISE that is deployed in the cloud and then using them to access Cisco ISE that is deployed in other cloud environments through unsecured ports. A successful exploit could allow the attacker to access sensitive data, execute limited administrative operations, modify system configurations, or disrupt services within the impacted systems.
    Note: If the Primary Administration node is deployed in the cloud, then Cisco ISE is affected by this vulnerability. If the Primary Administration node is on-premises, then it is not affected.

    Severity: 9.9 | CRITICAL

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    Tips for Hosting Your Client’s WordPress Website

    June 17, 2025

    Elevate marketing intelligence with Amazon Bedrock and LLMs for content creation, sentiment analysis, and campaign performance evaluation

    May 9, 2025

    CVE-2025-30466 – “Safari Same Origin Policy Bypass”

    May 29, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.