{"id":708,"date":"2026-08-11T03:00:04","date_gmt":"2026-08-11T03:00:04","guid":{"rendered":"https:\/\/easyprotools.com\/blog\/?p=708"},"modified":"2026-08-12T10:36:20","modified_gmt":"2026-08-12T10:36:20","slug":"windows-11-installation-failed","status":"publish","type":"post","link":"https:\/\/easyprotools.com\/blog\/windows-11-installation-failed\/","title":{"rendered":"Windows 11 Installation Failed? 15 Common Errors & How to Fix Them"},"content":{"rendered":"
\n
\n

Few things are more frustrating than watching an installation progress bar freeze, only to be greeted by a message stating that windows 11 installation has failed. Whether you are upgrading an existing PC, performing a clean install, or troubleshooting a machine that will not boot after a failed attempt, these interruptions rarely explain themselves in plain language. Instead, you get a cryptic hexadecimal code or a vague reference to a system file that could not be found.<\/p>\n<\/div>\n

This guide translates those messages into plain English. We will walk through fifteen of the most common causes behind a windows 11 failed to install error, explain exactly what triggers each one, and provide the specific steps that resolve them. Along the way, we will also cover what to do when your PC enters a windows 11 automatic repair loop, how to use windows 11 recovery mode effectively, and which tools genuinely help when standard troubleshooting is not enough.<\/p>\n

\n

Overview<\/span><\/p>\n

Why Windows 11 Installations Fail More Often Than Windows 10 Did<\/h2>\n<\/div>\n

Before diving into specific fixes, it helps to understand why windows 11 installation error reports increased noticeably compared to previous Windows versions. Microsoft introduced stricter hardware requirements for Windows 11, including mandatory TPM 2.0 support and Secure Boot compatibility, both of which did not factor into Windows 10 installations at all. A significant share of installation failures trace directly back to these requirements not being properly enabled in a system’s firmware, even on hardware that is technically capable of supporting them.<\/p>\n

Beyond hardware requirements, Windows 11’s installation process performs more validation checks throughout the process than earlier versions did, checking driver compatibility, available storage, firmware settings, and the integrity of downloaded installation files at multiple stages rather than just once at the beginning. This added scrutiny catches more problems, but it also means more installations halt partway through rather than completing with hidden issues that surface later. Understanding this context makes the specific errors below easier to diagnose, since most trace back to one of these categories: hardware compatibility, corrupted files, insufficient permissions, or a conflict with existing system configuration.<\/p>\n

\n

Diagnostics<\/span><\/p>\n

“Windows 11 Installation Has Failed” Messages<\/h2>\n<\/div>\n

A generic windows 11 installation has failed message, without a specific error code attached, typically appears during either a clean install from USB media or an in-place upgrade attempt. The first step in diagnosing this type of failure is checking the installation log files, which Windows generates automatically during setup and stores in predictable locations depending on which stage of the process failed.<\/p>\n

For clean installs performed from bootable media, pressing Shift and F10 simultaneously during setup opens a command prompt, from which you can navigate to X:\\Windows\\Panther to review setupact.log and setuperr.log. These files record exactly which component or check caused the failure, often referencing a specific error code that narrows the problem down considerably. For in-place upgrades performed through Windows Update or the Installation Assistant, similar logs are stored under C:\\Windows\\Panther after the failure, accessible once you are back at the desktop of your previous Windows installation.<\/p>\n

A generic failure without a specific code most commonly points toward one of three culprits: insufficient free disk space, particularly if your system reserved partition or EFI partition is nearly full; a corrupted or incomplete download of the installation media itself, which is common with USB drives created on unstable connections; or a conflict with third-party antivirus software that intercepts and blocks system-level file operations during setup. Ruling out each of these systematically, starting with disk space and a fresh installation media download, resolves a meaningful share of unexplained failures before you need to dig into specific error codes.<\/p>\n

\n

Common Errors<\/span><\/p>\n

Error 1: Windows 11 Error 0x80070002<\/h2>\n<\/div>\n

Windows 11 error 0x80070002 is one of the most frequently reported installation and update failures, and it translates to a straightforward underlying issue: the system could not locate a file it expected to find. Microsoft’s own documentation confirms this error generally points to missing or corrupted files, or an update that was previously interrupted before completing fully.<\/p>\n

The most reliable fix begins with the built-in Windows Update Troubleshooter, accessible through Settings, System, Troubleshoot, Other troubleshooters. This automated tool identifies and repairs many instances of this error without requiring manual intervention. If the troubleshooter does not resolve it, manually resetting the Windows Update components often succeeds where the automated tool falls short. This involves stopping the Windows Update, Background Intelligent Transfer, Cryptographic, and MSI Installer services through an elevated command prompt, renaming the SoftwareDistribution and Catroot2 folders, then restarting those same services. This process clears out any corrupted update cache files that may be triggering the error, giving Windows a clean slate to attempt the installation again.<\/p>\n

Error 2: Windows 11 Error 0x800f081f<\/h2>\n

Windows 11 error 0x800f081f corresponds to a more specific technical cause, officially designated CBS_E_SOURCE_MISSING. In practical terms, this means Windows Update attempted to install a component but could not locate the required source files, often within the system’s component store.<\/p>\n

This error frequently traces back to minor corruption within the Windows component store itself rather than a problem with your internet connection or the update file. The most effective fix involves running two built-in repair tools in sequence: System File Checker, invoked by typing sfc \/scannow into an elevated command prompt, followed by the Deployment Image Servicing and Management tool if System File Checker alone does not resolve the issue. Running DISM \/Online \/Cleanup-Image \/RestoreHealth allows Windows to repair the underlying image using Windows Update as a source, addressing corruption at a deeper level than System File Checker can reach on its own. It is also worth noting that free third-party antivirus software is frequently implicated in triggering this specific error, so temporarily disabling non-Microsoft antivirus protection during the update attempt is a reasonable troubleshooting step, provided you re-enable it immediately afterward.<\/p>\n

Error 3: Windows 11 Error 0xc1900101<\/h2>\n

Windows 11 error 0xc1900101 is almost always tied to driver incompatibility, making it one of the more predictable errors to diagnose, even though pinpointing the exact offending driver can take some patience. This error typically appears during the later stages of installation, when Windows attempts to migrate existing drivers to the new operating system version and encounters one that is outdated, corrupted, or fundamentally incompatible.<\/p>\n

Resolving this error starts with updating every driver you can identify as outdated, particularly graphics drivers, storage controller drivers, and network adapter drivers, since these three categories account for a disproportionate share of 0xc1900101 failures. Visiting your hardware manufacturer’s website directly, rather than relying solely on Windows Update to supply drivers, often surfaces newer versions that resolve the conflict. If updating drivers does not help, temporarily disconnecting non-essential peripherals, including external hard drives, printers, and secondary monitors, before attempting the installation again removes potential conflict sources one at a time. For particularly stubborn cases, performing the installation in Safe Mode with Networking bypasses many third-party drivers entirely, allowing the installation to complete before you reintroduce peripherals and confirm which one was responsible.<\/p>\n

Error 4: Windows 11 Error 0x80070005<\/h2>\n

Windows 11 error 0x80070005 signals an access denied condition, meaning the installation process attempted an operation it did not have sufficient permissions to complete. This is fundamentally different from the file-corruption errors covered above, since the underlying files are usually intact; the system simply could not access or modify them due to a permissions conflict.<\/p>\n

The first troubleshooting step is confirming you are running the installation or update process with full administrator privileges, since a standard user account, even one with apparent admin rights displayed in Settings, sometimes lacks the elevated permissions Windows Update genuinely requires. Right-clicking the installer and selecting “Run as administrator” resolves a portion of these cases immediately. Beyond that, corrupted user account permissions on core system folders, particularly the Windows and ProgramData directories, can also trigger this error. Running the System File Checker and DISM commands described earlier often repairs the underlying permission structure alongside any associated file corruption, since both tools reset system files to their expected, correctly permissioned state during the repair process.<\/p>\n

\n\n\n\n\n\n\n\n\n
Error Code<\/th>\nPrimary Cause<\/th>\nFirst Fix to Try<\/th>\n<\/tr>\n<\/thead>\n
0x80070002<\/td>\nMissing or corrupted files; interrupted prior update<\/td>\nWindows Update Troubleshooter, then reset update components<\/td>\n<\/tr>\n
0x800f081f<\/td>\nMissing component store source files<\/td>\nSFC \/scannow, then DISM \/RestoreHealth<\/td>\n<\/tr>\n
0xc1900101<\/td>\nIncompatible or outdated driver<\/td>\nUpdate graphics, storage, and network drivers; disconnect peripherals<\/td>\n<\/tr>\n
0x80070005<\/td>\nAccess denied due to insufficient permissions<\/td>\nRun installer as administrator; repair system file permissions<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Error 5: Insufficient Disk Space<\/h2>\n

A remarkably common cause behind a stalled or failed installation is simply running out of free storage space partway through the process. Windows 11 requires a minimum of 64 gigabytes of storage, but that figure represents the bare installation footprint, not the temporary space needed during the upgrade process itself, which can briefly require considerably more as old and new system files coexist during the transition.<\/p>\n

Checking available space before attempting installation, and clearing out unnecessary files if you are close to the minimum threshold, prevents this failure from occurring in the first place. Disk Cleanup, accessible by searching for it directly in the Start menu, can reclaim significant space by removing temporary files, previous Windows installation backups, and other accumulated clutter. If your system reserved partition specifically is undersized, a problem more common on older machines originally set up with Windows 7 or 8, resizing that partition through Disk Management may be necessary before installation can proceed successfully.<\/p>\n

Error 6: TPM 2.0 and Secure Boot Not Enabled<\/h2>\n

Among hardware-related causes, a missing or disabled Trusted Platform Module, along with Secure Boot not being active, accounts for a substantial share of installation failures on machines that are technically capable of running Windows 11 but were never configured correctly in firmware. Many motherboards manufactured within the past several years include TPM 2.0 support built directly into the chipset, but ship with it disabled by default since earlier Windows versions did not require it.<\/p>\n

Resolving this requires entering your system’s UEFI firmware settings, typically accessed by pressing a specific key such as F2, F10, Del, or Esc during startup, though the exact key varies by manufacturer. Once inside, look for settings labeled TPM, PTT (Platform Trust Technology, Intel’s implementation), fTPM (AMD’s equivalent), and Secure Boot, enabling each one if currently disabled. After saving these changes and restarting, the Windows 11 installer should recognize your hardware as compatible without further modification, provided your processor otherwise meets the minimum generation requirement.<\/p>\n

Error 7: Windows 11 Installation Stuck at a Specific Percentage<\/h2>\n

A windows 11 installation stuck partway through, particularly one that appears frozen at a specific percentage for an extended period, causes understandable anxiety, since it is often unclear whether the process is genuinely stalled or simply working slowly in the background.<\/p>\n

The most frequently reported instance of this is windows 11 setup stuck at 46 percent, a specific point in the installation process where Windows performs a substantial file migration and driver installation step. In most legitimate cases, this stage genuinely takes longer than surrounding stages, sometimes twenty minutes or more depending on storage speed, and patience alone resolves it without any intervention. However, if the percentage has not moved at all for more than an hour, and disk activity indicators show no ongoing read or write activity, the installation has likely genuinely stalled. At that point, a forced restart is reasonable, though it is worth noting that interrupting Windows during certain phases can leave the system in a state requiring recovery tools to restore to a bootable condition, which is covered in more detail later in this guide.<\/p>\n

Error 8: Corrupted or Incomplete Installation Media<\/h2>\n

When installation media, whether a USB drive or ISO file, becomes corrupted during creation or download, the resulting failures can appear at almost any stage of the installation process, making this cause frustratingly difficult to pin down through symptoms alone.<\/p>\n

The safest way to rule this out is recreating your installation media entirely, using Microsoft’s official Media Creation Tool rather than a manually copied ISO, since the tool verifies file integrity throughout the download and creation process. If you are creating bootable USB media, using a high-quality USB drive rather than an older or lower-quality one reduces the risk of write errors during the creation process that later manifest as installation failures. Running the media on a different USB port, ideally a native USB 3.0 port on the motherboard rather than a front-panel header or hub, also eliminates a surprisingly common source of intermittent read errors during setup.<\/p>\n

Error 9: Antivirus and Security Software Conflicts<\/h2>\n

Third-party antivirus and security suites, while valuable for day-to-day protection, are a well-documented source of installation interference, since many of them hook deeply into system-level file operations in ways that can conflict with the installer’s own file handling.<\/p>\n

Temporarily disabling third-party antivirus software before attempting installation, then re-enabling it immediately after the process completes successfully, resolves this category of failure in a meaningful number of cases. Windows Defender, Microsoft’s built-in protection, is designed to coexist smoothly with the installation process and generally does not require disabling. If you are uncertain which security software might be interfering, temporarily uninstalling it entirely, rather than just disabling it through its interface, provides a more thorough test, since some security suites continue running background services even when their main interface shows as disabled.<\/p>\n

Error 10: Incompatible or Outdated BIOS\/UEFI Firmware<\/h2>\n

Outdated motherboard firmware occasionally causes installation failures that have nothing to do with Windows itself, particularly on systems that have never had their firmware updated since original purchase. An older UEFI version may not correctly report hardware capabilities to the Windows installer, causing it to fail compatibility checks even on hardware that is genuinely capable of running Windows 11.<\/p>\n

Checking your motherboard or laptop manufacturer’s support website for the latest available firmware update, and applying it before attempting installation again, resolves this less common but genuinely frustrating category of failure. This step is particularly worth prioritizing if your system passed the PC Health Check compatibility tool previously but still fails during actual installation, since that specific pattern often points toward a firmware reporting discrepancy rather than a genuine hardware incompatibility.<\/p>\n

\n

Boot Loops & Recovery<\/span><\/p>\n

Understanding the Windows 11 Automatic Repair Loop<\/h2>\n<\/div>\n

A windows 11 automatic repair loop occurs when your system attempts to boot, fails, automatically triggers the built-in repair process, and then fails again, repeating this cycle indefinitely without ever successfully reaching the desktop. This is distinct from a standard installation failure, since it typically happens after an installation has technically completed, or after an interrupted update leaves the system in a partially updated state.<\/p>\n

This pattern, sometimes described interchangeably as a windows 11 boot loop, most commonly stems from corrupted boot configuration data, a failed driver update that prevents the system from initializing correctly, or file system corruption on the drive containing the operating system. Breaking out of this cycle requires accessing windows 11 advanced startup options, which involves interrupting the automatic repair attempt three times in a row by holding the power button during the boot process, forcing Windows to present the advanced recovery menu instead of continuing to attempt automatic repair.<\/p>\n

Once inside advanced startup, navigating to Troubleshoot, then Advanced options, provides access to several tools capable of breaking the loop. Startup Repair, Windows’ automated diagnostic and repair tool, should be your first attempt, since it specifically targets the boot configuration issues that commonly cause this exact symptom. If Startup Repair does not resolve the loop, System Restore, provided a restore point exists from before the problem began, can roll the system back to a previously functional state without affecting personal files stored outside the system partition.<\/p>\n

Using Windows 11 Recovery Mode Effectively<\/h2>\n

Windows 11 recovery mode encompasses a broader set of tools than automatic repair alone, and understanding what each option actually does helps you choose the right one rather than attempting fixes randomly in hopes something works.<\/p>\n

Within the Advanced options menu, Command Prompt access allows direct manual repair using tools like bootrec, which rebuilds the boot configuration data store, and chkdsk, which scans the drive for file system errors and attempts to repair them. Running bootrec \/fixmbr, followed by bootrec \/fixboot and bootrec \/rebuildbcd in sequence, resolves a large share of boot loop scenarios by rebuilding the boot records from scratch rather than attempting to patch whatever corruption exists in the current configuration.<\/p>\n

System Image Recovery, another option within this same menu, restores your entire system from a previously created backup image, provided you had the foresight to create one before problems began. This option requires an external drive containing the backup image and effectively reverts your system to exactly the state it was in when that backup was made, files and all. For situations where no restore point or backup exists and other repair attempts have failed, “Reset this PC,” found under Troubleshoot rather than Advanced options specifically, offers a middle ground between full recovery and complete reinstallation, allowing you to reinstall Windows while choosing whether to keep personal files or remove everything entirely.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Recovery Tool<\/th>\nBest Used When<\/th>\nAffects Personal Files?<\/th>\n<\/tr>\n<\/thead>\n
Startup Repair<\/td>\nSystem stuck in boot loop; boot configuration suspected corrupted<\/td>\nNo<\/td>\n<\/tr>\n
System Restore<\/td>\nA recent driver or update caused the failure; restore point exists<\/td>\nNo (system files only)<\/td>\n<\/tr>\n
Command Prompt (bootrec, chkdsk)<\/td>\nManual, targeted repair of boot records or disk errors<\/td>\nNo<\/td>\n<\/tr>\n
System Image Recovery<\/td>\nA full backup image exists from before the failure<\/td>\nReverts to backup state<\/td>\n<\/tr>\n
Reset This PC<\/td>\nOther repair options failed; reinstallation is the only remaining option<\/td>\nOptional \u2014 choose keep or remove files<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Creating and Using a Windows 11 Recovery USB<\/h2>\n

Preparing a windows 11 recovery usb before you actually need one is one of the most effective steps you can take to avoid being stranded without options during a serious boot failure. This drive contains the recovery environment separately from your main installation, meaning it remains accessible even if your primary drive’s own recovery partition becomes damaged or is unavailable for any reason.<\/p>\n

Creating this drive requires access to a separate, currently functioning Windows machine, since you cannot create recovery media on the same computer that is currently failing to boot. Search for “Create a recovery drive” within Windows Settings on the working machine, and follow the guided prompts, ensuring you check the option to back up system files to the recovery drive if you want the resulting USB to be capable of full reinstallation rather than repair tools alone. A drive of at least sixteen gigabytes is generally required when this option is selected, since the additional system files add considerably to the space needed compared to a repair-only recovery drive.<\/p>\n

Once created, booting from this drive on the affected machine requires accessing your system’s boot menu, typically through a function key pressed during startup, and selecting the USB drive as the boot device ahead of the internal storage. From there, the same recovery environment tools described in the previous section become available, run entirely from the USB media rather than relying on a potentially damaged recovery partition on the internal drive.<\/p>\n

\n

Diagnostic Tools<\/span><\/p>\n

Windows 11 Repair Tools Worth Knowing<\/h2>\n<\/div>\n

Beyond Windows’ own built-in recovery environment, several tools genuinely add value when standard repair options are insufficient or when you want a more guided, less command-line-intensive troubleshooting experience.<\/p>\n

\n

Windows 11 Media Creation Tool<\/a><\/h3>\n

Microsoft’s own Media Creation Tool remains the most reliable starting point for creating fresh, verified installation media when corrupted media is suspected as the root cause of repeated failures. It downloads installation files directly from Microsoft’s servers with built-in integrity verification, considerably reducing the odds of a corrupted download compared to sourcing an ISO from a third-party site. Beyond creating bootable USB drives, it can also perform an in-place upgrade directly, which is often the fastest path to repairing a Windows installation that boots successfully but exhibits persistent corruption-related errors, since it replaces system files while preserving personal data and installed applications.<\/p>\n<\/div>\n

\n

Windows Sysinternals Suite<\/a><\/h3>\n

For more advanced diagnostic work, particularly when trying to identify exactly which driver or process is interfering with an installation, Microsoft’s Sysinternals Suite provides a collection of free, official utilities that go considerably deeper than built-in Windows tools. Autoruns, one of the suite’s most useful components, reveals every process and driver configured to launch at startup, making it far easier to identify a suspicious or conflicting third-party component that standard Task Manager views would not surface clearly.<\/p>\n<\/div>\n

\n

Best Practices<\/span><\/p>\n

Preventing Future Windows 11 Boot Issues<\/h2>\n<\/div>\n

Once you have resolved a failed installation or recovered from a boot loop, a handful of preventive habits meaningfully reduce the odds of encountering windows 11 boot issues again in the future.<\/p>\n

Creating a system restore point manually before installing major updates, rather than relying solely on Windows’ automatic scheduling, ensures a reliable rollback option always exists immediately before any change that carries elevated risk. This takes only a few moments through the System Properties panel and provides meaningful insurance against update-related failures.<\/p>\n

Keeping drivers current, particularly for graphics cards, storage controllers, and network adapters, addresses one of the most common root causes behind both installation failures and post-update instability. Checking manufacturer websites directly every few months, rather than relying exclusively on Windows Update to supply driver updates, catches compatibility improvements that Windows Update sometimes takes longer to surface.<\/p>\n

Finally, maintaining a current backup, whether through a full system image or simply ensuring important files are synced to cloud storage or an external drive, transforms even a catastrophic failure requiring complete reinstallation from a genuine crisis into a manageable inconvenience. The peace of mind this provides is worth the modest time investment required to set up automated backups once, rather than scrambling to recover irreplaceable files after the fact.<\/p>\n

When to Consider a Clean Install Instead of Repair<\/h2>\n

Sometimes, after exhausting reasonable repair attempts, a clean installation genuinely represents the faster and more reliable path forward, particularly for systems that have accumulated years of software installations, driver conflicts, and registry clutter on top of whatever specific error initially prompted the troubleshooting effort.<\/p>\n

A reasonable rule of thumb is to attempt no more than two or three targeted repair approaches, such as those described throughout this guide, before pivoting to a clean install if the underlying error persists. Continuing to chase deeper and deeper troubleshooting rabbit holes on a system that may have accumulated compounding issues over years of use often costs more time than simply backing up personal files and starting fresh. Before committing to this route, confirm your backup is complete and verified, since a clean install removes all existing applications and settings, preserving only what you have explicitly backed up beforehand.<\/p>\n

\n

Frequently Asked Questions<\/h2>\n<\/div>\n
\n

What does it mean when I see “windows 11 installation has failed” without an error code?<\/h4>\n

A generic failure message without a specific code typically points to insufficient disk space, corrupted installation media, or antivirus software interfering with the setup process. Checking the setup logs in the Panther folder, freeing up storage space, and recreating your installation media with the official Media Creation Tool resolves most cases of this kind.<\/p>\n<\/div>\n

\n

How do I fix a windows 11 automatic repair loop?<\/h4>\n

Interrupt the automatic repair process three times in a row by holding the power button during startup, which forces Windows into the advanced startup menu instead of continuing to attempt repair automatically. From there, try Startup Repair first, followed by System Restore if a restore point exists, and use Command Prompt tools like bootrec to manually rebuild boot configuration data if both options fail to resolve the loop.<\/p>\n<\/div>\n

\n

Is it normal for Windows 11 setup to get stuck at 46 percent?<\/h4>\n

Yes, this specific stage involves substantial file migration and can genuinely take twenty minutes or longer depending on your storage speed, so brief pauses at this percentage are typically not a sign of failure. If there has been no disk activity and no progress for more than an hour, however, the installation has likely stalled and a restart followed by fresh installation media is the recommended next step.<\/p>\n<\/div>\n

\n

Should I create a windows 11 recovery usb before I actually need one?<\/h4>\n

Yes, creating recovery media in advance, while your system is functioning normally, ensures you have a reliable repair and reinstallation option even if your system’s internal recovery partition becomes damaged or inaccessible. This process takes only a few minutes through Windows Settings on a currently working machine and provides essential insurance against future boot issues.<\/p>\n<\/div>\n

\n

When should I use a windows 11 repair tool versus performing a clean install?<\/h4>\n

Repair tools like Startup Repair, System Restore, and DISM are worth attempting first, since they resolve the underlying issue without erasing personal files or installed applications. If two or three targeted repair attempts fail to resolve a persistent windows 11 installation error, a clean install, performed after backing up important files, is often the faster and more reliable path forward.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Few things are more frustrating than watching an installation progress bar freeze, only to be greeted by a message stating […]<\/p>\n","protected":false},"author":1,"featured_media":754,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[26],"class_list":["post-708","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-windows"],"_links":{"self":[{"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/posts\/708","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/comments?post=708"}],"version-history":[{"count":4,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/posts\/708\/revisions"}],"predecessor-version":[{"id":753,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/posts\/708\/revisions\/753"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/media\/754"}],"wp:attachment":[{"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/media?parent=708"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/categories?post=708"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/easyprotools.com\/blog\/wp-json\/wp\/v2\/tags?post=708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}