Post-DISM start, minimal boot delay in Windows 11 25H2
Post-DISM start, minimal boot delay in Windows 11 25H2
Hello. I'm running Windows 11 Home version 25h2. About a month ago I installed Windows 11 and on January 28, 2026 I did the following: I opened Settings, chose "Clean Temporary Files" and checked all boxes. After that, the system restarted. Then I launched CMD with admin privileges and executed the command to clean temporary files: C:\Windows\System32> Dism /Online /Cleanup-image /Startcomponentcleanup The process began at 60% and finished at 70%. It took roughly 30 seconds to an hour before it completed successfully. After that, the computer restarted once more. When I ran the cleanup again, the C:\Windows\Logs\Cbs\Cbs.log file was regenerated from the beginning. I checked if the WinSxS folder had changed using Dism /Online /Cleanup-image /AnalyzeComponentStore, but no modifications were detected. Following these steps, my boot time increased by 2 to 3 seconds; repeated restarts, clearing %temp% and %windir%\temp were done, yet the delay remained. This slow startup persisted despite optimizing Windows 11 with the best settings and using an NVMe M2 SSD. I also looked into the Event Viewer to find the issue, but no errors were found. To test for corruption in the WinSxS repository, I ran Dism /Online /Cleanup-image /Checkhealth, which reported no problems. I appreciate any guidance on resolving this and improving the boot performance.
Open the command prompt and execute sfc/scannow. This will fix or fetch any missing or damaged files on your system. Please inform me of the outcome and ask for further assistance if needed.
Thank you for your response. Nonetheless, sfc/scannow and similar techniques aren't detecting any issues.
I examined all components for hardware problems. The BIOS version is current, and the event viewer was also checked. No issues were found in the event viewer either. It seems the delay occurred solely because of the cleanup process. Essentially, this issue appeared only after the cleanup was completed.
Thank you for your message. It seems there may not be any corruption detected in the system files. Perhaps a feature update could help resolve the issue? Since no components appear to be affected, it might be worth checking that.
This entire message feels quite unclear. It seems you're questioning the purpose of this action right after starting a fresh installation. The timing and details raise some confusion—how did this come up so quickly? I'm trying to understand how it's being measured and why such a brief period matters. There are hints of online research that might have influenced this, but I want to focus on using the PC properly instead of jumping into complex tasks.
Hello, I would like to address your questions point by point: Why? → I performed these steps as part of regular system maintenance. Why on a fresh installation? → Even on a clean install, this helps ensure that residual or unnecessary files are removed. Regarding the 2–3 second delay: → This is significant to me because I have previously experienced serious issues with Windows 11, including SSD failures. Since I am now using a new SSD, I want to determine whether the delay is software-related rather than hardware. After POST? → Yes, the delay occurs during the boot sequence immediately following the BIOS POST. Measurement and concern: → I measured the delay manually without specialized tools. My intention is not simply to worry about a minor time difference, but to investigate whether this behavior indicates a potential bug in Windows 11 or if it is expected system behavior.
Hmm, it's unclear if I can assist you since we don't share similar thoughts. Still, good luck! (system functioning properly)