Internal Error Occurred In Rpc
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “An internal error occurred in a remote procedure call (RPC)” whenever I try to run an .exe file (and System Restore isn't working anymore) up vote 0 down vote favorite I'm a bit inexperienced, and I'm having a bit of a problem. I keep getting the error message "An internal error occurred in a remote procedure call (RPC)" when attempting to run certain programs. This happened after I downloaded and ran a program of, in hindsight, dubious authenticity. What are the steps I should take to diagnose and fix this problem? Currently running Windows 8. EDIT: I attempted to open System Restore. Received error message "System Restore could not start." EDIT2: Attempting to run a program by clicking on it spits out that error message, but, say, downloading an .exe file and clicking on it in my browser's downloads works just fine. What the hell? windows-8 download system-restore rpc share|improve this question edited Feb 12 '15 at 17:51 asked Feb 12 '15 at 16:15 Von Donitz 12 certain programs = ? dubious program = ? –meatspace Feb 12 '15 at 18:18 Try in Safe Mode to start... If you look in the registry to see what's set to open EXE files (HKEY_CLASSES_ROOT\exefile\shell\open\command), what's there? –Ƭᴇcʜιᴇ007 Feb 12 '15 at 18:23 possible duplicate of How can I remove malicious spyware, malware, viruses or rootkits from my PC? –DavidPostill Feb 12 '15 at 18:25 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By post
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why am I getting an exception whenever I use the CFileDialog? up vote 3 down vote favorite 1 Whenever I run my application under the debugger, I http://superuser.com/questions/877149/an-internal-error-occurred-in-a-remote-procedure-call-rpc-whenever-i-try-to get the following exception when using CFileDialog to browse for a file to open First-chance exception at 0x769db9bc in MyApp.exe: 0x000006BA: The RPC server is unavailable. First-chance exception at 0x74e8cd99 in MyApp.exe: 0xC0020043: An internal error occurred in RPC. MyApp.exe has triggered a breakpoint This happens using VS2008 on Windows 7 64 bit, it doesn't happen doing the same thing under XP. There are no useful symbols on the call stack indicating why this is happening, and http://stackoverflow.com/questions/7267090/why-am-i-getting-an-exception-whenever-i-use-the-cfiledialog I can avoid the problem simply by turning off exceptions in the debugger, but I'm wondering why this is happening and how to avoid it. c++ exception mfc share|improve this question asked Sep 1 '11 at 7:15 Shane MacLaughlin 14.8k762120 add a comment| 2 Answers 2 active oldest votes up vote 12 down vote accepted First-chance exception messages can be safely ignored. In this case, this is part of Windows API internal implementation. Exceptions are thrown and caught somewhere. You need to turn off only first chance exception break in the debugger. share|improve this answer edited Sep 5 '11 at 6:22 Serge Wautier 14.6k104695 answered Sep 1 '11 at 7:21 0123456789 24.2k2191156 add a comment| up vote 4 down vote Just to add to Alex's answer above, the exception can be ignored. To do this under VS2010, do the following; Debug / Exceptions Add, type is Win32 exception, number 0x6ba Go to Win32 exceptions, and untick thrown under 6ba This allows you to keep other exceptions active during debugging share|improve this answer answered Oct 13 '11 at 7:06 Shane MacLaughlin 14.8k762120 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, y