Main Forum > General Computer Support

Windows installer could not accessed

<< < (2/3) > >>

Boggin:
Can you boot up into the advanced boot options and select Repair your Computer then navigate to the Windows Recovery Environment (WRE), making a note of the OS's location then select Command Prompt.

You need to make a note of the OS location as it may not see it as C:

Enter (assuming C) - dism.exe /image:c:\ /cleanup-image /revertpendingactions

exit (to close the cmd window)

Then Restart.

For the msiInstaller Event ID 1014 it would seem the msiexec.exe cmd should be run in Safe Mode, but as the confirmation is for the Windows Installer service to be running, I'm not sure if that would resolve anything - but give it a go.

https://technet.microsoft.com/en-us/library/cc735564(v=ws.10).aspx

For the .NET Runtime Optimization error, I've seen where updating/reinstalling the Network drivers has stopped that error from appearing.

Go to the driver vendor's support site for those.

For the chkdsk /f that is the standard window you would get after entering that cmd.

Type and enter Y as prompted then enter shutdown /r /t 00 and wait for it to do its thing then view the report as I've previously described.

A chkdsk repair cannot be carried out while the volume is in use - i.e. after you have booted Windows so it must be done on the next restart before Windows loads.

Did you run mrt.exe to check for any infection ?

tarvi4:
Unfortunately, everything I did what you recommended didn't help, it seemed to make matters even worse.
This windows installer thing is messing with my brain so im just gonna call the IT guy to install a new windows for me.
I did chkdsk, that lead to bad memory pool.
I did the image whatever thing, that caused my computer to not start at all.
I dont know what caused this computer to randomly mess it self up, but I surely wont be using windows 7 ever again!
Even though I couldn't fix the problem, thank you for helping me. I learned alot about fixing stuff etc.

Boggin:
The dism cmd shouldn't have caused that.

Does the machine boot up at all ?

If it doesn't, see if it will boot up into the advanced boot options to navigate to the WRE again and try Startup Repair.

If at first that fails, you can run it up to 3 times.

If it does boot up, can you download HDSentinel to see what it reports about the state of your HDD, as a failing HDD can give the bad pool memory error.

Also if the chkdsk finds bad clusters and there isn't enough space on the HDD, you can also get that error.

While this is a paid for program, using the green download button will get you the 30 day trial version.

http://www.hdsentinel.com/

If you do have to take it in, then tell the guy about the bad pool memory error, or log onto the forum so he can see what you have experienced and tried.

tarvi4:
Im back, with the problem fixed throught a clean windows 7 install.
I showed him some pictures of my struggles & your suggestions.
He tried to resolve the problems again with no result.
Then eventually, he compared the registry files with his own computer and he found out my Windows files had been tampered(the windows that came with the computer), so a clean windows 7 fixed the problem, but I still had clean my HDD of files to be safe.
He tested the HDD and RAM for anything suspicous with the HDSentinel and found nothing.
So to anyone who reads, if you have the same problem and tried everything to your limits, do a clean windows 7 install or a system restore before the problem occured.

Boggin:
As he had a Win 7 install disk, I'm surprised he didn't do an offboot sfc /scannow which would have compared your system files with those of an incorrupt source, but should the corruption have been because of an infection then the clean install would be the way to go.

Do you still have Win 7 x64 Pro ?

May be a good idea to download Belarc Advisor and make a note of the product key he used for future ref.

http://www.belarc.com/free_download.html

Navigation

[0] Message Index

[#] Next page

[*] Previous page