When attempting to install an ArcGIS product, the installation may fail and an error is returned similar to the following:
C:\users\<username>\AppData\Local\Temp\pb13177D50\pbcore.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000022.
This error is usually caused by an access problem triggered either by a specific application, or by Windows. The error can be triggered by files that are unsupported, corrupted, or are inaccessible.
Procedure
There are several approaches to this issue:
Run Checksum on the affected file(s)
See: How To: Verify an Esri download using the checksum
Scan for corrupt files
The SFC utility scans the machine hard disk to check for potential corrupt files that may cause the error.
Follow these steps to launch SFC
- In the Windows Search box, type cmd.
- Right-click Command Prompt and click Run as Administrator.
- Type: sfc /scannow, and press Enter.
Information such as the following may be returned:
Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.
- Follow the instructions to determine the cause of the issue.
Check for permission issues
If the application causing the error is known, check the permissions configuration to ensure these are set correctly.
Follow these steps:
- Right-click the application that caused the error. This can either be the shortcut on your Desktop, or the .exe file of the application, available in This PC.
- Click Properties.
- Navigate to to the Security tab.
- Change permissions for Administrators, Authenticated Users, and System to Allow Full Control.
- Click Apply.
Uninstall and re-install ArcGIS If you have installed software from another party that has updated ArcGIS with unsupported or corrupt libraries, it is recommended that you uninstall that software and ensure that your ArcGIS install has rolled back to a known state with valid libraries, or reinstall it from the original Esri software install files.
If you have received an installation of ArcGIS with these modified/unsupported libraries already in place, you may want to contact your software supplier or corporate Information Technology department to report the problem – These files may have been modified from the original software distribution.
Hi All.
Windows XP SP3 {Mingw - do not know how to establish version of Mingw Qt 2010.05 QtCreator 2.0.1 } These three installed together from a single download
Qwt 6.0.0-rc5
Very new at this. This is the first of two different queries that I will post separately. Here goes ... Am an old, unreformed and unrepentent C programmer that has not programmed in many years. Am aware of C++ concepts such as classes, inheritance, polymorphism, overloading but not yet comfortable with these concepts.
When I create and build an app (just learning stuff, nothing important) from within Qt Creator it will run OK when started from Qt Creator or from a command prompt (Haven't got the hang of Qt Creator yet and haven't figured out how to do a release build in Qt Creator yet). If built as either 'debug' or 'release' from a command prompt it will run OK from the command prompt. If built as 'debug' from the command prompt it will run OK if started from Windows (Explorer). However if built as 'release' from the command prompt and run from Windows it will produce the following error 'The procedure entry point _Z5qFreePv could not be located in the dynamic link library QtCore4.dll.'
There are two, different QtCore4.dll files in the Qt install. Both have version 4.7.0.0 but they differ in size. QtCore4.dll version 4.7.0.0 2.18MB located in c:\qt\2010.05\bin QtCore4.dll version 4.7.0.0 2.41MB located in c:\qt2010.05\qt\bin
I can copy either into the app's directory but the error remains when I try to start the app from Windows. With the smaller of the two dlls in the app directory, starting the app from the command prompt results in the same error. With the larger there is no error when starting from the command prompt.
To summarize... Debug builds - all OK, no matter if started from Windows, command prompt or from within Qt Creator Release build - will start OK from command prompt but not from Windows
I am sure that I must have installed something not quite right or am doing something silly now.
Any ideas?
Take care.
Mike