Running unelevated 64-bit Windbg would lead you to the following messages

Once 64-bit Windbg is run elevated, the debugging driver can be installed successfully (unless something else gets in the way). You may see messages like the following from the system when the debugger attempts to install 1394kdbg.sys and succeeds at it.

After the debugging driver is installed, you can switch back to unelevated 32-bit Windbg to debug your target without 0×80004005 errors.

Tagged with →  
Share →

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop us a note so we can take care of it!


Which WDK macro to assert is better ?

Loading ... Loading ...
Set your Twitter account name in your settings to use the TwitterBar Section.