Windows 10: Repair MS .doc file from Mac

I have an MS .doc file (note NOT .docx) that's become corrupted. I'm using a Mac but it won't open the file either in Pages or Preview. I've also tried opening it in Libre office but, again. it can't open it.

I've used Stellar Recover to recover the .doc although it's not the recovery that's the problem, it's the corruption of the file and, again, it can't fix it.

Has anyone got any suggestions to fix the corrupted file - I don't want to pay for new software?

Thanks in advance

 

microsoft word 2003

I have a lot of ms word files on my pc. But one of them showed me an error - Getting unknown error messages while opening (.doc) or (.docx) files. I don't know how to open my word file or repair microsoft word. Any suggestions, guys, please.

 

Corrupted file RAR

If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:

• Open WinRAR application in your system.
• Now click on File tab > Open or simply press Ctrl+O.
• A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
• Now click Open button.
• Click Tools tab > Repair archive or simply press Alt+R.
• Again a small window "Repairing File name.rar" will pop up.
• Now click Browse to select a location to save the repaired archive.
• Check the box "Treat the corrupt archive as RAR" and click OK.
• WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.

I hope the above steps will help you repair the corrupted RAR archive.

Thanks.

 

Unable Search for .odt (LibreOffice Docs) file formats using File Contents.

Hello,

I just want to let you know that the search still does not work.

I have also tried the File Explore by using a keyword, ".odt: keyword."

The result shows only .odt doc files with names which include the keyword.

No .odt doc files which contain the keyword in the body.

As mentioned in the original post, I have done everything that was suggested including:

1. Run the DISM Tool.
2. Run the System File Checker utility.

I hope that someone knows how to resolve the issue.