Recommended Posts

I installed Windows 7 on a partition with no problem at all. Everything worked flawlessly until my most recent reboot.

Every time I select Windows 7 to boot from, it does a disk check. It will NOT let me do anything to skip it as it would normally (press any key to skip CHKDSK). It completes the CHKDSK operation, reboots, select windows 7...it starts all over again. It's a consistant loop and I'm completely unaware as to how I would go around fixing it.

If all else fails I'm just going to do another clean installation, but for the moment it's getting on my nerves.

Any ideas as to what may have caused this?

Thanks,

Rollinup

Link to comment
https://www.neowin.net/forum/topic/721802-issue-with-windows-7-beta-and-chkdsk/
Share on other sites

My test system did the exact same thing yesterday, when I powered it up.

I was able to skip the CHKDSK, but upon booting into windows, I found that my secondary partition (D:) had been totally corrupted. I had to delete the partition and re-build it... thankfully there wasn't anything of importance on there.

Hi, I had the exact same problem, what I did was just enter Windows 7 with "The last known good boot" option.

After that I was abre to use the OS, but I had some problems after that, like messages saying "Corrupt files", and somes url's didn't load.

Later!

PD: If you guys find a better solution, please tell it here :)

Hi, I had the exact same problem, what I did was just enter Windows 7 with "The last known good boot" option.

After that I was abre to use the OS, but I had some problems after that, like messages saying "Corrupt files", and somes url's didn't load.

Later!

PD: If you guys find a better solution, please tell it here :)

I forgot one thing, after that, go to "start button" and write on the box chkntfs /X C: (In my case C: is where Windows 7 is installed), and afther that, you'll never have that problem.

I tried booting into Windows 7 by selecting the "last known good configuration" option, and it worked. Although I still got some messages about the drive having some corruptions, so I had to run chkdsk again, and this time the "last known good configuration" didn't work - it still ran chkdsk. So in the end I formatted my Windows 7 partition and reinstalled. It's fully working now.

Ok, I found the solution to this problem.

Before installing windows 7, what we have to do is format the disk where we're going to make the installation using windows 7 dvd, not a program like norton or something like that.

I did that and now i'm not having more troubles :)

  • 2 weeks later...

I have been using Windows 7 since build 6801. I am currently using build 7000 just as most of you are. In Beta 1, CHKDSK is broken. I have submitted a bug to MS on this.

Here is what the bug report says:

Bug ID: 405406

Schedule Disk Check does not occur on reboot

Description

Schedule Disk Check does not occur on reboot. Asking for a disk check or CHKDSK is ignored on restart of Windows 7.

>>>>> Additional information entered by submitter <<<<<

Please see the IssueSteps.zip file for repro steps as recorded by the person submitting this bug.

Repro Steps

Attempting to use System Restore and it indicates there is an error on Disk C. I select the option to do a disk check on restart. However, no checking occurs on restart.

No one has entered a bug report about the CHKDSK loop issue. I will if someone will provide me the repro steps and a proper description of the issue.

My CHKDSK is working fine but AVG antivirus was causing a dirty shutdown, as a result files were being corrupted, check in Computer Managment/Event Viewer/Windows Logs/System for critial errors, they were at the very start of the boot process and were being caused by AVG, shut AVG it off and no more problems.

Forgot, running 64 bit Win 7

  • 2 weeks later...

Folks,

How many of you, has or had ever installed Diskeeper 2009 on their W7 installation?

And, how many of you has or had ever used its "Boot Time Defragmentation"?

Now, how many of you has or had ever used that "Defragment the MFT" option?

I strongly believe that there exists no bug in the common functions of CHKDSK in W7, but the real cause for entering CHKDSK on every reboot is the fact Diskeeper has not matured enough to learn to behave in W7's presence. :crazy:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Because Chrome is doing it. And no one said anyone had to update immediately. That's silly. They could update every day for all I care as long as it's fast, and the next time the browser restarts, you're good. And the basic point is not to tee it up for bigger updates. As it is right now, all the windows I had open reopen anyway except inprivate.
    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!