Why does Windows take a lot longer to boot after performing a disk che

[CurlyWhirly]

I've often wondered this.

Any idea why this happens ?

I am referring to the Windows disk check as shown in my screenshot (below):

On Vista it takes over 3 times as long to boot up !

It only seems to be the boot-up immediately after the disk-check is done as any boot-ups afterwards go back to normal loading times - strange

[D4\/!d]

I very rarely perform this check. So I wouldn't know how long it takes to reboot.

How come you need to run the check often enough to know it takes longer to reboot.

Mystified.

B)

[CurlyWhirly]

I very rarely perform this check. So I wouldn't know how long it takes to reboot.

How come you need to run the check often enough to know it takes longer to reboot.

Mystified.

B)

I'm mystified as well !

What occasionally happens on Vista (not the Windows 7 SSD drive installation) is that I get a warning from within Windows that Windows needs to check the disk for consistency but after the disk-check is complete there are no bad sectors just trivial changes to O/S disk structure.

Yet using SMART disk monitoring, nothing shows when this alleged consistency problem occurs so it must be a false alert

[rong]

It's you that likes Vista

[CurlyWhirly]

It's you that likes Vista

Yes I do which is why I've still kept it despite upgrading to Windows 7.

In my opinion it's a fault of the SMART disk monitoring utility and is not the fault of the O/S as the (occasional) disk check gives it a clean bill of health.

[bludgard]

I know that if I have a machine with a multi-boot setup or one that has a virtual machine installed, it tends to issue these disk check notifications more frequently than a single install machine. I actually never get the chkdsk boot-screen unless I have multiple OSs installed.... Have you run diagnostics with hard drive specific program?

[-pops-]

It may be that the

trivial changes to O/S disk structure

are sufficient to confuse the system and it has to search around for where to open.

[CurlyWhirly]

It may be that the

trivial changes to O/S disk structure

are sufficient to confuse the system and it has to search around for where to open.

So are you saying that these could be causing the consistency warnings ?

If so this would explain it.

[CurlyWhirly]

I know that if I have a machine with a multi-boot setup or one that has a virtual machine installed, it tends to issue these disk check notifications more frequently than a single install machine.

It's funny you should mention this as this is exactly what happens !

I've had more consistency warnings in the last month (since I went to a dual-boot system) than the last year.

Have you run diagnostics with hard drive specific program?

No but that's a good idea.

I'll try and find one from the Samsung website as that's the drive that has Vista installed.

Thanks.

[D4\/!d]

I know that if I have a machine with a multi-boot setup or one that has a virtual machine installed, it tends to issue these disk check notifications more frequently than a single install machine.

It's funny you should mention this as this is exactly what happens !

I've had more consistency warnings in the last month (since I went to a dual-boot system) than the last year.

Alright you've lost me.

I have a multi boot machine [xp pro/Win7x32/Win7x64]

I have NEVER seen an consistency warning. How come?

[CurlyWhirly]

Alright you've lost me.

I have a multi boot machine [xp pro/Win7x32/Win7x64]

I have NEVER seen an consistency warning. How come?

Dunno

[Belatucadrus]

Maybe the asymmetric signal digitiser has been re-polarised by the inverted flux of negative 64 bit particles running through the bus from the CMOS battery.

If so you could try turning it upside down and beating it with a big stick until it behaves itself. I've tried this approach with several PCs, doesn't do the computers much good but I somehow always feel MUCH better.

[bludgard]

Maybe the asymmetric signal digitiser has been re-polarised by the inverted flux of negative 64 bit particles running through the bus from the CMOS battery.

If so you could try turning it upside down and beating it with a big stick until it behaves itself. I've tried this approach with several PCs, doesn't do the computers much good but I somehow always feel MUCH better.

Belatucadrus wrote:

“If so you could try turning it upside down and beating it with a big stick until it behaves itself.”

Do you think if I run over it a couple of times with the steel tracks of a bull-dozer it would straighten out? Before I run out and apply this workaround, are we talking about the CMOS, CMOS battery, or the machine itself?

Ah, hell, I can’t sit around waiting for an answer all day. I’ll just throw all machines beneath the tracks and see how everything gets sorted. Thanks for the info and insight. I’ll let all my school buddies know about this fix.;)

[Belatucadrus]

I’ll let all my school buddies know about this fix.;)

A useful testing technique as it will conclusively tell you which of your friends have the common sense of a rabid moose and should not be trusted out with sharp or pointy objects let alone a computer.