Windows 10: Unusual Message at Startup

Since creators update was installed a couple of days ago, I've been seeing this message on the screen during boot up, "Scanning and repairing drive , (followed by a bunch of things in parentheses), then ending with 100%" Then the machine finishes booting up. This happens all the time when powering up. Any idea why this message appears? And, is it important? Thanks.

:)

 

Message at Startup

I am getting a RunDLL message on the desktop at startup. "There was a problem starting C:\Program. The specified module could not be found." I have run scan, no threats found. This is Windows 10. The message started appearing after last update.

 

Message at Startup

To make sure, run a malwarebytes Scan:

Free Cyber Security & Anti-Malware Software

 

Right click on your main drive, Properties.
Click the Tools tab.
Press the Check button.
Press Scan drive.

 

I did that and was notified that the scan wasn't necessary because the drive is OK. Anyhow, that message on startup isn't causing a problem. Just wondering why it's there.

 

You right, it's strange to see odd new things that don't look familiar. If I were you, I would also be curious to what that could be.
See if you can take a picture of it with an external device (such as a smart phone/digital camera) and uploading it to here. That would help out narrow down what it could be.

 

Hi, this implies the dirty bit is set on that volume, which triggers chkdsk on reboot. Windows thinks there is some file system corruption and has set this bit.
Fsutil dirty

At an admin command prompt try
fsutil dirty query c:

If it's set, chkdsk will run (to check the integrity of your file system).
Of course, the idea is that running chkdsk will clear it.

Try this
Post the result of running chkdsk at boot which you can get after a restart as follows:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
or
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
Make sure the result is clear or fixed- else do not proceed.

and inspect the report generated to see what it says about your disk.

Also, check your physical disk:
Download install and run Hard Disk Sentinel (trial)
Post a screenshot of its GUI.
to post a screenshot please use the Insert Image icon above your post to the left of the video icon

Note: resetting the dirty bit manually is possible, but there is no 'Windows' way to do this. You have to use a hex editor - plenty written up on the internet. For C: this cannot be done on line- you need to use a boot disk such as Kyhi's (available from the top of the Software and Apps section here).

It's possible someone has written a utility to do this of course.

 

Windows 10 Check Disk at every startup since creators update Solved - Windows 10 Forums

Another thread on it and disabling hibernation solved the issue for me.

 

At an admin command prompt try
fsutil dirty query c:

Thanks I did that and got message: volume C is NOT dirty. I'll see if I can photograph the message at next startup. It doesn't last very long, perhaps 5 seconds or so.

 

I don't have hibernation enabled.

 

Now, this is also strange. Previously, I was always able to reach command prompt by right clicking on the start button. Now there is no dialogue for both command prompt and command prompt admin. Is it time to reset the computer or just leave well enough alone? After all, my machine is operating normally despite these glitches. Advice?

 

Mr. Ed,
MS replaced it with PowerShell ... Should be able to change it back ... Settings / Personalization / Taskbar / Replace Command Prompt with PowerShell in Menu bla, bla ... turn it off.

 

Try this. Right click an empty space on the Desktop, select Personalization, then click Taskbar from the left menu and turn off 'Replace command prompt with Power Shell'.

 

Thanks, Eagle. I'm not too familiar with power shell, but I'll take your suggestion. BTW, I just reset my computer and reinstalled my programs. I'm still getting that mysterious message at start-up. I'll try to photograph it in the near future so I can post it here.

 

Eureka! That worked, Essenbe. Thanks for the advice....Ed