Windows 10 "Smoni Failed to create empty document

How do I correct this error.  I have a lot of riched32.dll files.  How do I know if any should be deleted?

Hello Walter,

Thank you for posting your question on Microsoft community.

I appreciate you for providing details about the issue.

I would suggest you to perform clean boot and check if it helps.
Refer this article:
How to perform a clean boot in Windows
https://support.microsoft.com/en-us/kb/929135
(Also holds good for Windows 10)

Clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program.

Note: After you have finished troubleshooting, follow these steps from section “How to reset the computer to start as usual after clean boot troubleshooting” to reset the computer to start as usual.

I hope this information helps.

Please do let us know if you need any further assistance.

Thank you

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you.  It seemed to be working fine now without the message.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

After performing the "first major update" for Windows 10, I now get that "failed to create empty document" error message in the "Smoni" box when I do a cold boot (obviously it doesn't appear if I come out of hibernation). 

Anyway, I performed the "clean boot" procedure by hiding all the MS services and disabling what remained, etc. but when I rebooted, the message still appears, so obviously it isn't the stuff I disabled.  What now?  Is there some other way to determine the source of this error message?

Since nothing was changed prior to downloading and installing this major update, doesn't this point to the fact that it's probably something in this update that's causing the issue?  Your help is greatly appreciated!  (At this point, it doesn't seem to be a "problem" in that it's not affecting anything else on the system.  This has occurred on all the computers in my household; laptops and desktops, both running Home and Pro versions, most are 64-bit.)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Same problem here.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated January 3, 2024 Views 8,202 Applies to: