This issue occurs because the boot plan for the ReadyBoot feature exceeds the size limit of 512 kilobytes (KB). Each restore point creates a snapshot of Windows that Volsnap.sys must validate during the startup process. When you create many restore points, the boot plan for the ReadyBoot feature eventually exceeds the size limit of 512 KB, and cannot be stored. Therefore, startup I/O operations are not precached, and the startup process is slow.
Note The boot plan is stored in the following registry entry:
Note: There may be additional causes that result in your PC starting up slower than expected that are unrelated to excessive System Restore Points. This issue can also happen if the boot process is loaded with a large amount of items. Example: You have a large amount of startup items, including startup applications running in the background, hardware drivers being loaded, and applications set to start when you start your PC.
To check for the issue with Restore Points, look in the Event viewer for the following Event Log.
Log Name: Microsoft-Windows-ReadyBoost/Operational
Event ID: 1016
Task Category: ReadyBoot
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.