Message "Aborted." Between Windows Splash Screen and Welcome Scree

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After the Windows Loading screen (the black screen with the windows logo and
the
progress bar) I recieve a message on a blue screen that says "Aborted." and
nothing
else. The screen is not the BSOD. It resembles the screen you get when you
run chkdsk
at next boot. After this the screen goes black for a second. Then the
Welcome screen
comes on and windows finishes loading normally. No other performance issues
or problems
are noticable.

I would like to know what is being aborted and how I can stop this message
from appearing.

So far I havn't been able to find any help online even from microsoft's
Knowledge
Base. I have used my "System Mechanic 6" to check the start up programs. I
looked
in the Startup Folder, all the "run" keys in the registry, scheduled tasks,
msconfig, and all my other programs that can be set to run at startup.
(maybe i missed something?) I can't find anything.

I suspect that somewhere in the system a process, program, or system utility
may
have been enabled at every boot with a blank or corrupt entry, or had been
set to
run only if certain parameters are met (sort of like some defrag programs
can be
set to only defrag at a certain amount of fragmentation).
 
Thank you for your time. I am sorry I didn't get back to you sooner.

Here are the steps I have already taken. I am sorry I didn't mention them
in my initial post.

scanned for viruses, malware, adware, spyware, trojans, rootkits, and many
other types of "nasties" that can plausibly do this to a system. I used
various free and retail scanners to do so. I found one exploit, "byteverify"
and removed it from my system, "hopefully". So thank you for that suggestion,
however the annoyance still exists.

I checked the scheduler to see if anything was scheduled to run at
Next-Boot. I didn't observe anything out of the ordinary there.

I thought, "Okay, what programs do things on Next-Boot?" I came up with at
least three MS diskdefragmenter, chkdsk, and last but not least my Utility
Suite.

I checked the settings of each of these and there are no settings set to
start at next-boot.

Trying to dig deeper for clues, I restarted with boot logging enabled. When
I looked at the boot log, I noticed a few drivers with a "Did not Load".
"Aha!" I said, "Whats this?" Only after a little research I found out these
drivers were not loading because they were not needed. During my research on
the Not loaded drivers, I was told to check the registry for these drivers to
confirm what they were for. Sooooo....

I decided to check my registry for all entries having to do with chkdsk,
defrag, etc.
After I looked at all the chkdsk entries, I didn't notice anything out of
the ordinary.
Another light bulb clicked on. (smacks forehead homer simpson style "Doh")

I could have just restored the registry from one of my back ups. I went
back to a month ago, because i knew it was working then. I Restarted the
computer a couple times. And..........

THE ANNOYANCE WAS STILL THERE! GRRRR!

Sorry about that outburst. Anyway, concluding from all I had done
previously, I think something maybe stuck in the MBR? Who knows?

I went back and rechecked my Utility Suite's settings and found one that had
to do with defragmenting the registry on next-boot or every restart. It was
set to every restart. "Doh!!" I set it to the only other setting available.
Next-Boot only.

I restarted the computer and now I get a new message in the same spot. "Your
utility suite is preparing to defragment the registry." It starts with the
System Hive.
When it finishes with that, the dreaded word comes up again, "Aborted."
Then windows starts normally. It must have something to do with my Utility
Suite then.
I will keep trying different settings, or even uninstalling and reinstalling
my Utility Suite. However, right now. I am tired of trying to fix this and
need to take a break from it for a while.

Again,
Thank you for your time.
 
Back
Top