|
There are isolated problems with current patches, but they are well-known and documented on this site. |
I had my W7 Pro computer set to run chkdsk this morning and it ran fine but on reboot (after the windows splash screen) I now get “ers program not found skipping autocheck” and then it continues to boot to windows. I get that same message on every reboot now.
Anybody have a clue what happened????
Don't take yourself so seriously, no one else does 
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Check to see if the file chkdsk.exe is in System32
Yes, it is.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Are you sure that chkdsk completed successfully? What you see on the screen is not necessarily what is sent to Event Viewer. EV – Windows Logs – Application Scroll down to Event 1001 – Wininit Read carefully!
Yes, the event viewer shows that it ran successfully.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
@cadesertrat , do you intend for chdsk to run on every boot? What method did you use to request the successful first run? The method, or syntax, used may give an indication of what is happening now.
No, I do not run chkdsk on every boot, I run it about once a month. I’ve been doing that since the computer was first built in 2013.
The method I have always used is right click cmd and choose Run as Administrator, and type in chkdsk /f and it has always run just fine.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I ran SFC and it found nothing and I ran chkdsk again a little while ago, which ran fine but I still get that same message after the Windows splash screen appears and just before I put in my password to start windows.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Please check the following location in RegEdit.exe:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager::BootExecute
Would you please post the exact string in the BootExecute value here?
This location is sometimes used by malware, it is also used by autocheck, and some AV and Defrag utilities.
The default value with no other third party utilities is a simple
autocheck autochk *
(Note the space between autochk and the * . . . )
Standard disclaimers about making changes in RegEdit apply: take a backup first!
Here’s a screenshot of one of mine, that shows the default value plus an entry for a commercial defrag utility.
~ Group "Weekend" ~
Here is Boot Execute:
Also, this morning I got this at startup so had to go into BIOS but don’t have a clue what to change so saved and exited.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
It looks like ers.exe is a Trojan which your AV program probably mostly zapped. You need to edit the registry entry to remove the “autocheck ers” line. When you reboot, go into BIOS by typing F1. In BIOS, you probably will find either “Load Defaults” or “Load Optimized Settings” under one of the menus, usually under the Save and Exit menu. The “Load Optimized Settings” is the one to choose. Then select Save and Exit.
Once you are back in Windows, you might want to download the free version of MalwareBytes and run its default scan. MalwareBytes should find and either fix or remove any other registry entries which are related to the Trojan.
CADR – in response to your startup BIOS message anomaly posted above … I see you’re using an ASUS Motherboard.
Please refer to my previous post here about a similar BIOS boot message anomaly I experienced a while back. In summary …
I also use an ASUS motherboard (though an earlier version based on the X58 Chipset) in a system I built in 2010-2011 that began having intermittent BIOS bootup messages.
Though my BIOS boot message anomaly was slightly different than yours, the first time it happened, I got into BIOS, set defaults, rebooted & all was well so I gave it no further thought.
A few months later, it happened again so I repeated setting up defaults then rebooting & again everything appeared normal.
Over the next 6 months or so, the # of occurrences kept increasing until finally I couldn’t get the system to boot.
Thinking I had suffered a catastrophic hardware failure, I then completely tore the system apart troubleshooting everything & finding nothing wrong, put it back together but it still wouldn’t boot.
After literally tearing the system apart in an effort to diagnose what had failed, I ultimately discovered that my CR2032 CMOS BIOS Battery had become … WEAK ?
As it measured 2.71 Vdc (still works great in my GMC Key Fob), I went ahead and replaced it with a fresh CR2032 measuring 3.1 Vdc and lo & behold … all systems GO !
Maybe ASUS has an unknown (or known but undocumented) issue with some of their batches of BIOS CMOS memory chips they use on their boards that require batteries with a charge greater that 2.7Vdc otherwise one or more BIOS “bits” may lose their “1” or “0” bit charge and therefore fail their corresponding BIOS bit checksum calculations which in turn would result in the expected “Go to Setup to Recover BIOS Settings” message at system boot.
Normal indication of a bad BIOS battery usually results in the wrong or lost date setting & I’ve seen this a few times on legacy Compaq, HP & ThinkPad Laptops with batteries that were at/below .8 Vdc.
But my experience with my ASUS P6T Deluxe V2 board indicates to me that, I will lose one or more BIOS “bits” causing corrupt BIOS settings & the corresponding failed BIOS checksum long before my RTC resets to 1980.
If this happens again, I would suggest checking / replacing your CR2032 CMOS BIOS Battery with a fresh one.
Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS
Yeah, that’s a valid point. Actually I just replaced the battery on my girlfriends ASUS MB about a month ago.
She kept getting the same screen that I am getting on mine and after finally realizing that her BIOS date and time were Waayyy off, I figured it out. It’s certainly possible that my battery is getting low since 2013.
The date and time on mine seem to be fine so far so will have to wait and see if I still get the same boot up screen.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Here’s a shot without the edit window open;
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Go ahead and remove the line in the BootExecute value, but be certain to leave the default value intact as listed above. ( autocheck autochk * )
Recommend a full scan with MalwareBytes or another second opinion version.
Also possible this is a leftover from Norton – a very old version.
~ Group "Weekend" ~
Looks like it’s trying to auto-launch ers.exe – google that executable name, and you’ll find a few sites that believe it’s a trojan.
Check your anti-malware logs to see if something by that name was recently removed from your system.
It looks like ers.exe is a Trojan which your AV program probably mostly zapped. You need to edit the registry entry to remove the “autocheck ers” line. When you reboot, go into BIOS by typing F1. In BIOS, you probably will find either “Load Defaults” or “Load Optimized Settings” under one of the menus, usually under the Save and Exit menu. The “Load Optimized Settings” is the one to choose. Then select Save and Exit. Once you are back in Windows, you might want to download the free version of MalwareBytes and run its default scan. MalwareBytes should find and either fix or remove any other registry entries which are related to the Trojan.
I checked in MSE logs and there is nothing listed there as being removed. I already have/use MalwareBytes free and I have looked at the reports there and there is no record of anything being removed. So nothing has been removed that I can find.
To your advice of “Load Optimized Settings”, yesterday I updated the BIOS in the hopes of curing the BIOS message at startup and after the BIOS reboot I went in to the BIOS and loaded the Optimized Settings as per the ASUS advice for doing that.
Next point is that I’m wondering if it is safe to just go in and delete the autocheck ers line as I’m a bit hesitant to play with the registry.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Next point is that I’m wondering if it is safe to just go in and delete the autocheck ers line as I’m a bit hesitant to play with the registry.
Yep, it’s safe to remove that line. As mentioned above, do leave the default value intact as the one and only line remaining.
~ Group "Weekend" ~
Go ahead and remove the line in the BootExecute value, but be certain to leave the default value intact as listed above. ( autocheck autochk * ) Recommend a full scan with MalwareBytes or another second opinion version. Also possible this is a leftover from Norton – a very old version.
I’ve never used Norton so am unsure where that would come from?
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Then more likely you suffered a partial infection attempt – something was mostly blocked but some system settings were touched before your AV stopped it.
Ok, I guess I’ll attempt to get rid of that line. I assume that I just double click on the Boot execute and in the box (that I previously posted) just put the cursor in and backspace it until that entry is gone, is that correct?
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Correct. When you are done it should look like this:
~ Group "Weekend" ~
Ok, I cleared that entry in the edit box and got a warning, which I clicked ok on.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Once again, with feeling: you MUST leave the default value intact. See above posts by me please. You only want to remove the entire line with “ers” – but leave the other line.
~ Group "Weekend" ~
I rebooted the computer and the message didn’t appear during boot up so evidently that was the cure thanks to all.
Do I still need to go to the BIOS and reload the Optimized Settings again??
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Do I still need to go to the BIOS and reload the Optimized Settings again??
I doubt it? That one comes under the belief that if it’s not broken no need to fix. 
~ Group "Weekend" ~
Is the BIOS still asking you to hit F1 when you boot your computer? If so, then yes. You also might have a weak BIOS battery.
Once again, with feeling: you MUST leave the default value intact. See above posts by me please. You only want to remove the entire line with “ers” – but leave the other line.
Yes, that line is still intact. I just checked it again to make sure.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Just as a followup, I did some more googling and found this http://blog.condusiv.com/post/2009/12/30/Program-not-found-skipping-AUTOCHECK-revisited.aspx
I have an older version of Diskeeper (now owned by Condusive) on the W7 computer and it looks at the Boot process so it may have found that entry in the registry to kick that error message. That still doesn’t explain where the reg entry came from in the first place though.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Is the BIOS still asking you to hit F1 when you boot your computer? If so, then yes. You also might have a weak BIOS battery.
Yes, it did it again this morning on a cold boot. It seems to have the correct time and date though so I’m a bit confused as to why it keeps doing that. I guess I need to get around to changing the 2032 battery to see if it will boot without the F1.
I don’t use it that much so I have been putting it off
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Wow, Changing the CMOS battery was quite an adventure!
After changing the battery, I booted up and got the F1 screen so I changed back to my set profile and saved/exited and it booted into windows.
In the hidden icons on the notification area there was nothing and no internet icon. I checked for internet and it said that it was connected so I brought up Admin cmd and set it to run chkdsk and rebooted. Most everything was back in the notifications but I noticed the clock was way off so I opened that up and saw that it was Dec. 2008!!!!
I manually updated the clock and everything went into high gear on the computer for about 5 minutes and then settled down. I have never had that happen when changing the 2032 battery on a MB before. The battery said that it is good till 03/2024 but maybe I should have checked it.
I guess I’ll wait and see if it boots alright tomorrow on a cold boot.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I see that CADesertRat’s motherboard an ASUS P8Z77-V Pro with ACPI BIOS revision 2104. I Googled the motherboard model and found it on the ASUS web site.
Here ia a link to the overview page:
https://www.asus.com/us/Motherboards/P8Z77V_PRO/overview/
Here ia a link (PDF) for the User Manual:
https://dlcdnets.asus.com/pub/ASUS/mb/LGA1155/P8Z77-V_PRO/E7198_P8Z77-V_PRO.pdf
Referring to the user manual…
Page 3-2 shows that you can you can type F5 or click on the “Default (F5)” button to load optimized defaults.
Page 3-26 shows that the default is Disabled for all Wake on LAN settings.
To reload all BIOS Optimized Defaults…
1. Reboot and repeatedly hit the DEL key (once per second) until you enter the BIOS, or type F1 if the F1 message is being displayed.
2. Load the Optimized Defaults by typing F5 or clicking on the “Default (F5)” button. Alternatively, you an go to the Exit menu. Under the Exit menu, you can click on “Load Optimized Defaults”
3. Then click on the “Save Changes & Reset” as shown on page 3-35.
@GTP, thanks for taking the time to look that up.
This morning it booted up without the F1 window and when I updated the BIOS to 2104 the other day, I loaded Optimized Defaults on the subsequent boot so that should be set already.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
You’re welcome. Sounds like you are good to go!
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
