Unhandeld WPF 4.0 CP Exception

A customer of mine has the following strange exception.

The problem is, that I can't reproduce it on any of my machines. Everywhere it runs fine, even on a fresh Win 7 64bit installation.

Problemsignatur:

  Problemereignisname:                       CLR20r3
  Problemsignatur 01:                          mysoftware.exe
  Problemsignatur 02:                          2.20.000.0
  Problemsignatur 03:                          4e5d24bc
  Problemsignatur 04:                          PresentationFramework
  Problemsignatur 05:                          4.0.0.0
  Problemsignatur 06:                          4d930fa2
  Problemsignatur 07:                          a34
  Problemsignatur 08:                          46
  Problemsignatur 09:                          System.IO.IOException
  Betriebsystemversion:                        6.1.7601.2.1.0.256.1
  Gebietsschema-ID:                             1031
  Zusatzinformation 1:                          0a9e
  Zusatzinformation 2:                          0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:                          0a9e
  Zusatzinformation 4:                          0a9e372d3b4ad19135b953a78882e789

EDIT:

The error message is strange, because it tells:

Exception:
System.IO.IOException: Die Ressource "app.xaml" kann nicht gefunden werden.
   bei MS.Internal.AppModel.ResourcePart.GetStreamCore(FileMode mode, FileAccess access)
   bei System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)
   bei System.IO.Packaging.PackagePart.GetStream()
   bei System.Windows.Application.LoadComponent(Obje开发者_C百科ct component, Uri resourceLocator)
   bei xxx.App.InitializeComponent()
   bei xxx.App.Main()

Which is really strange, because at the most other PCs, the App has no problem to show up.

Could someone point my to the right direction please? Thanks in advance

---

As it says something about an IOException it might be that the customer or customer's system has been using a file that the application would have liked to modify or something similar.

---

I once had a similar exception. It would occur when a particular WPF window would load for the first time.

After a lot of digging, I found the cause of the exception was that the WPF window was using a 3rd party UI control that referenced a few unmanaged dll files, and the unmanaged dll files were not present on the user’s PC.

---

Might have to do with permissions for that particular user. Does the error occur for all users on the same machine?

We had a strange WPF problem once which was due to old graphical driver versions on that machine. Even got a BSoD a couple of times.