Jump to content
Posted 09 December 2006 - 00:57
Posted 09 December 2006 - 14:38
Posted 29 July 2008 - 05:11
Posted 12 September 2008 - 05:36
Open up a command prompt from your recovery options and copy C:\Windows\System32\winevt\Logs\Application.evtx to an external disk.
Posted 15 November 2008 - 04:51
Hello. I know this thread is super old, but I have not found a solution to this anywhere on the web, and I finally figured out how to solve this problem. Maybe somebody will find this useful.
Posted 15 November 2008 - 14:26
Posted 28 February 2009 - 15:26
Posted 16 July 2009 - 15:01
Posted 15 September 2009 - 14:47
Posted 30 December 2009 - 16:19
Many thanks to PJPoon for posting this fix! This problem began after uninstalling Kaspersky, which was blocking my internet access and then installing Avast!. Everything was working great until I rebooted, Interactive Logon Process Initialization Has Failed. I thought no, prob, system restore, copy over old registry hives from backreg folder, no problem. Nope! None of the Windows Repair options worked, tried them all. Typically I would try to look at the logs using Sysinternals ERD 2007, but its not compatible with Vista. There is an "unattach mode" which allows you to copy files, just can't use any of the tools or have access to the registry. So I copied the Application.evtx file to an external drive. I then attached it to another PC running Vista, copied the file to that PC and viewed the log. There were multiple Windows Logon Errors plus SidebySide errors. The SideBySide errors point to a file located in C:\windows\winsxs\manifests\x86_microsoft.windows.common(long string of numbers).manifest. I grabbed a copy of the file from the working Vista machine to the external drive. Went back to the broken machine and copied it, and presto! Logged In! I thought I was looking at a format. Thank you so much!!!!! But I think the machine may still have viruses...
Posted 24 February 2011 - 00:24
Posted 19 February 2013 - 14:17
Posted 19 February 2013 - 14:34
In the end, I managed to simply perform a system restore from the last critical update and the computer runs again. I still don't get what went wrong with the machine
Posted 19 February 2013 - 15:11
Why is this thread a collection of 1 post wonders? o_0