Share via

Run DLL error - printui.dll

Anonymous
2014-09-09T04:09:13+00:00

I continue to get a run dll error - "there was a problem starting printui.dll  The specified module could not be found."  I ran the System File Checker and these are my results below:

2014-09-08 23:32:03, Info                  CSI    0000084b [SR] Cannot repair member file [l:20{10}]"puiapi.dll" of Microsoft-Windows-Printing-ClassInstallerAndPrintUI, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2014-09-08 23:32:04, Info                  CSI    0000084d [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-09-08 23:32:05, Info                  CSI    0000084f [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-09-08 23:32:05, Info                  CSI    00000850 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"

2014-09-08 23:32:05, Info                  CSI    00000851 [SR] Cannot repair member file [l:20{10}]"puiapi.dll" of Microsoft-Windows-Printing-ClassInstallerAndPrintUI, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2014-09-08 23:32:05, Info                  CSI    00000852 [SR] This component was referenced by [l:350{175}]"Microsoft-Windows-Client-Features-Package-AutoMerged-printscan~31bf3856ad364e35~amd64~~6.3.9600.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-printscan-Deployment"

2014-09-08 23:32:05, Info                  CSI    00000853 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"??\C:\WINDOWS\System32"[l:20{10}]"puiapi.dll"; source file in store is also corrupted

How can I fix these files?

Thank you for your help!

Windows for home | Previous Windows versions | 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 No comments
Answer accepted by question author
  1. Anonymous
    2014-09-09T21:23:58+00:00

    Hi Sandy,

    Thank you for choosing Microsoft Community to post your question. I appreciate your knowledge in running System File Checker tool and posting the logs.

    Printui.dll is the executable file that contains the functions used by the printer configuration dialog boxes.

    Let’s run the Deployment Image Servicing and Management (DISM) tool which will try to fix the corrupt operating system files.

    a. Open an elevated command prompt. To do this, on the start screen type cmd, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

    b. Type the following commands. Press Enter after each command.

    DISM.exe /Online /Cleanup-image /Scanhealth

    DISM.exe /Online /Cleanup-image /Restorehealth

    c. Close the command prompt then check if it fixes the issue.

    Try this step and let us know the results. We’d be happy to help if you need any further assistance.

    10+ people found this answer helpful.
    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-12-03T18:03:03+00:00

    Hey Babu V,

    Thank you so much for this response, I looked all over and did not find the right thing, thank you so much!

    Greetings,

    Robbe

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2016-02-17T08:28:43+00:00

    it is taking long time after running first command to fix the issue. is there any other solution for this

    0 comments No comments
  3. Anonymous
    2015-03-18T04:10:31+00:00

    Hi Babu V,

    I ran the System File Checker and these were the results:

    2015-03-18 11:18:17, Info                  CSI    00000512 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-03-18 11:18:24, Info                  CSI    00000514 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-03-18 11:18:24, Info                  CSI    00000515 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
    I did not encounter Run DLL error. However, every time I open my laptop, a mysterious window suddenly pops-up and closes instantaneously at startup. A certain website recommends to perform System File Checker. I have also read a thread from this site that explained on how to manually replace corrupted files. I have no idea where to get good files to replace such corrupted files. How can I fix these files?
    
    0 comments No comments
  4. Anonymous
    2014-12-04T18:58:14+00:00

    Hi Robbe,

    We are glad to know that information provided was useful. Please feel free to reply, in case you

    face any other issues with Windows in future. Thank you for contacting Windows Community.

    0 comments No comments