Bad Office Update Triggers Chkdsk on Startup

[sandoz]

System: Windows 7 Ultimate, Microsoft Office Professional Plus 2016


I've run into a peculiar problem that resulted from a improper automatic Office Update. The automatic update did not fully load. Thereafter, none of the office components would launch. In addition, the chkdsk utility would launch upon startup but would not run to completion indicating that improper software was installed and that System Restore should be utilized.



I tried to use System Restore, but System Restore would not run. System Restore indicated that Chkdsk needed to resolve disc consistencies before the system could be restored to a previous restore point. I was able to repair Office. However, the Chkdsk utility continues to run on startup. I've tried entering command: chkdsk C:/r at the command prompt to run chkdsk with repair. But, the chkdsk utility will not run to completion upon startup.


So, the Chkdsk utility continues to initiate on startup but doesn't complete and I'm not able to use System Restore until the Chkdsk utility can run to completion to resolve disc inconsistencies that were created by the improper Office update.



Any suggestions?
Thanks, Sandoz

 

[AmericanPharaoh]

Hello, you might see if this below may be able to help by resetting chkdsk.

Check Disk - Reset

 

[sandoz]

Thanks for reply American Pharaoh. I'll try the options and get back to report on outcome.

 

[samuria]

If the dirty bit is set you cant stop chkdsk check if the dirty bit is set from a cmd prompt


fsutil dirty query C:

 

[sandoz]

American Pharaoh suggested 3 options. I appreciate his/her input. American Pharaoh suggested:

1. Cancelling the Chkdsk utility at the Command Prompt. It didn't work.

2. The second option suggested downloading file 'Reset_Chkdsk.Reg'. I don't feel comfortable messing with the Registry. If someone can convince me that this is a safe move, please opine and I'll give it a go.

3. The third option suggested editing the Registry. Like option #2, I'm not feeling confident about editing the Registry. I've done it on other occasions. But, the remedy could be worse than the problem.

 

[RolandJS]

"2. The second option suggested downloading file 'Reset_Chkdsk.Reg'. I don't feel comfortable messing with the Registry. If someone can convince me that this is a safe move, please opine and I'll give it a go."
If the source was from inside bleepingcomputer or sevenforums -- it is likely a safe way to go. Both forums are crowded with folks who are very good at what they do or teach.

 

[sandoz]

RolandJS
Thank you for the prompt. I'll try options #2 and #3 and get back to thread to inform about outcome.