📎 AI Summary:
The user "jeetenkushwaha" posts that after updating their BIOS on a Dell PC, they encountered a Windows 10 missing file error. Responses suggest running system file checks using commands like "sfc /scannow" and "dism /online /cleanup-image /restorehealth" to repair missing or corrupted files, with some advice to review BIOS settings. The original poster later confirms that their issue was resolved successfully, indicating a positive outcome after following the troubleshooting steps.

jeetenkushwaha

New Member
Joined
Mar 5, 2018
Messages
2
Thread Author #1
I Just Update my BIOS on my Dell Pc but I got a message on my pc: please repair your windows 10 some file is missing.
 

Last edited by a moderator:
Solution
Try these scans which can find and repair issues:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Try these scans which can find and repair issues:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
 

Solution

davehc

Essential Member
Premium Supporter
Joined
May 1, 2008
Messages
5,546
As Kemical advises.
I am thinking it may be something that has changed in the bios. I would suggest you open the bios and run through all the functions. It could be, but unlikely, the boot sequence.