Main Forum > General Computer Support
(Solved) 0xc0000142 error
Shane:
Not what so ever. I did research on the error and it has to do with missing or wrong version files. Once I am able to connect back to him I have a few things I am going to try.
Shane
bobothedragon:
Shane had worked for a long time and he has solved the problem. cmd is now working again and the error no longer pops up. Seriously, thank you very much for that! It'd be best for him to explain the situation. Thank you to Boggin as well for looking into the problem and replying to this thread.
*as a side note,Initially i tried to reset my computer following the instructions here http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03546603#N89 , which was absolutely useless
Now HP has another option here http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03489643 which uses the HP recovery manager. It seems to do more than the method above and may actually work.
Boggin:
Glad Shane was able to sort it for you.
For me, I would be interested as to how that could have happened and why the Reset which is supposed to replace the OS, didn't.....
Shane:
Only thing I can think of is when he tried to do the windows reset it would have needed cmd.exe to run, and so it failed to do it properly.
Here is the email I sent him on what I did, I had pulled a 36 hour programming session so I was rather out of it by the time I emailed him and he let me know it worked. lol
--- Quote ---I have no idea which part of what I did fixed it LOL, I was on the thing for 4 hours.
Here is some things I did but got to busy to type them in the notepad.
Reset all permissions in the registry and file system, that let me register files that where getting access denied, you will be able to run my windows repair now to reset the permissions back.
I copied over 400 or 500+ dll files to the system32 folder. I basically took all the dlls from my system32 and then copied them over, only copying the ones you didn't have out of 2700 dlls you didnt have close to 500 of them. Of course I am on 8.1 pro so hard to tell.
I then did a trick after all that, I ran windows disk cleaner, in the there is an option to clean up windows updates. What that does is goes through the winsxs folder removing old updates and outdated files. That took way longer than I have seen it take before I am curious if it might have been the trick or not, or if it was everything I did combined.
Oh and of course I got rid of macfee which freaking fought me the whole time, even though it was uninstalled it was still freaking running and scanning every file.
OH and I also downloaded and ran ccleaner, not to clean the drive, just to run the registry scan to find any registry keys that point to things that are no longer there, it found 1170.
--- End quote ---
Shane
Boggin:
Thanks Shane.
Perhaps the vendor factory reset would have been the one to run in this case.
Since a Windows Update Oct 2013, running Disk Cleanup as an admin in Win 7 has removed obsolete WUs, but wouldn't you have needed cmd.exe to have run that in Win 8.1 as well ?
I think if I'd put that sort of a shift in - I'd probably need a week off :smiley:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version