The error “The specified module could not be found” happening in Windows 11

Anonymous
2021-12-25T04:16:45+00:00

Upgraded one of my desktop PCs to Windows 11. I have a 2nd desktop still running Windows 10

On the Windows 11 desktop the “The specified module could not be found” error occurs. I notice that the error happens when attempting to access a jpeg or mp4

The error can be fixed in cmd window with these commands

C:\Windows\system32>  gpupdate /force

C:\Windows\system32>  sfc /scanfile=c:\windows\system32\ieframe.dll

C:\Windows\system32>  sfc /scannow

C:\Windows\system32>  exit

Restart

Unfortunately, the error eventually re-occurs on my Windows 11 desktop.

This error has never occurred on my Windows 10 desktop.

So, I'm beginning to think that this may be a "Windows 11" bug

Anyone else getting this error?

If so, have you found a permanent solution?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

49 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-04-21T16:30:52+00:00

    I was getting the error opening a jpg with "Photos" or an mp4 with "Movies & TV" - I could however continue to open jpg with Paint and movies with Quicktime. The error kept re-emerging after doing a "fix" - I did all of the fixes mentioned in this thread (except for the advice to re-install all of the drivers on my PC, when I got that advice from a Microsoft reply I concluded that they had no idea of root cause). The last time I got the error it was resolved after doing a Norton full system scan and Win11 updates - that was back in early March - the error has not re-emerged. I don't really know what caused the error or what has hopefully fixed it, wish I could be more helpful.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-04-21T15:53:06+00:00

    I have had this same issue as well and it's driving me nuts.

    Only started appearing once I upgraded to Windows 11 when Microsoft advertised it on my PC.

    The only thing I have noticed for certain is that this issue pertains specifically to opening images or audio files through the windows file explorer. I can still open an image if it's on my Desktop, or if I go into Task Manager and Restart Windows Explorer. Curious if the rest of you having this issue are noticing the same behavior. But I've been dealing with this for months now and i really just want it to get fixed

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-04-06T20:41:49+00:00

    I fixed it using the powershell command back on March 31, and it just started happening again today. The fix didn't work this time but I haven't tried restarting the machine yet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-03-11T19:20:36+00:00

    I haven't had the error for a few weeks as well

    It went away after I did a full norton scan, there have also been a few win11 updates

    Can't really discern what may have "fixed it"

    This is the longest I've gone with out getting the error since it started happening, so maybe its

    really fixed, time will tell...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-03-11T18:08:38+00:00

    I hear you it always comes back on me too. I just found this fix this morning. Still no error but let's see if I have to really it after a week or so. I will post up in a week or two to say if it's back or not

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments