c0000135 Error On Boot - %hs Missing

How would you know if the post is helpful if you didn't even try any of the steps? You'd best change you attitude before you're tossed out of here on your ear for insulting volunteers who are trying to help you.

You say in your OP that you do not run any except an obscure AV which immediately calls into question the possibility of infection, hence Best Practices are to disinfect with MBAM and install the recommended AV.

Since almost all DLL's are generated by a malfunctioning program at Startup, it's easiest to eliminate the error by establishing a Clean Boot. Kaktussoft suggested this earlier but was ignored so I repeated it and provided a tutorial which shows an easier way to achieve and keep it over the long haul.

There is no substitute for a perfect Clean Reinstall of Win7 which is a specialty of these forums and a gift I was offering you my help with since your efforts failed to the point you wanted to roll it back using windows.old.

If you speak rudely to another volunteer here you will quickly find youself tumbling in outer cyberspace. This is the top tech forums on the web with the foremost experts in numerous areas who will not put up with anything but grateful thanks or constructive criticism.

gregrocker said:

How would you know if the post is helpful if you didn't even try any of the steps? You'd best change you attitude before you're tossed out of here on your ear for insulting volunteers who are trying to help you.

How is what I said insulting? I simply asked if you read my posts because to me, it did not seem that way. Allow me to explain why your post was not helpful whether or not you think that I tried these methods already.

gregrocker said:

Run a full scan now with Malwarebytes.

Why do I need to do this? I do not have any viruses on this computer. It is a completely new installation of Windows 7. (See next line.)

gregrocker said:

Uninstall all other AV's, install Microsoft Security Essentials to run a full scan and keep it turned on and updated.

Why did you tell me to install Malwarebytes and then you tell me to remove it? Doesn't seem helpful. (See next line.)

gregrocker said:

Establish a Clean boot as suggested, then work through the other Troubleshooting Steps for Windows 7.

That was already said and I will try that as soon as I finish the Chckdsk and post the results to see if I am moving in the right direction.

gregrocker said:

If problems persist I would strongly consider getting a perfect Clean Reinstall - Factory OEM Windows 7 which steps are the same for retail.

I already did. I'm not going to reinstall Windows if I just reinstalled Windows. Unless of course, you didn't read my post where I said that I did that already.

What you said made me feel like I wasted my time by trying to give all of the information I could possibly give just for someone to skim over what I said. I'm not saying you didn't read it, but I had specifically stated that I had already reinstalled Windows and that the problem now resides within an old installation within the Windows.old folder. Malware Bytes and Windows Essentials will not be helpful in this situation because there is literally nothing on the computer except for the Windows.old folder and the other stuff that is directly placed on the hard drive by a new Windows 7 installation. Again, I have no qualms with anyone on this site; Everyone here seems intelligent and insightful.

The Best Practices for Win7 established over three years with near unanimity here is to have MSE installed while MBAM is kept onboard for on-demand scanning. If there is possibility of infection we recommend first MBAM - in Safe Mode if necessary - or Windows Defender Offline bootable CD. This should have been the first thing done with the .dll errors, followed by a Clean Boot to isolate the program responsible at boot which was the one step you ignored.

I didn't know if you still had your install or had already rolled it back, but since you had windows.old you had already reimported any infection that existed into the reinstall. This and your other early comments about AV security were a red flag.

What I did know is that you said your reinstall was not helpful in which case it's highly likely you didn't follow the best practices for getting and keeping a perfect Clean Reinstall - Factory OEM Windows 7 . I would read over it now to know for sure how close you came and strongly consider redoing it if necessary.

A Guy said:

crait said:

I feel that you did not even read my posts in this thread. This post is not helpful and I think that this forum has rules against spam. Thank you.

One of our hardest working volunteer members here tried to help you and you replied with the above. You did not do the suggested clean install he suggested as you said it worked until you revisited the windows.old, where you apparently reintroduced your original problem. I am not the expert in this many here are, but even I can see the fault in this.

A Guy

I now have Windows again, running on that computer which shows that the problem is not a hardware issue, especially with all of the checks that I've run on it already, and that the problem stems from the Windows.old.001 folder.

[This post is currently being edited.]