New
#1
Can not update to IE11 on Win7 Home
This has been going on for a long time. Could not upgrade to IE10, then IE11. All of the other updates work fine.
Getting the error 9c59. Hopefully someone can help
This has been going on for a long time. Could not upgrade to IE10, then IE11. All of the other updates work fine.
Getting the error 9c59. Hopefully someone can help
SFC shows the following problem...
I'll post a fix protocol for it a little later.Code:2014-06-27 14:33:07, Info CSI 000001d8 [SR] Repairing 1 components 2014-06-27 14:33:07, Info CSI 000001d9 [SR] Beginning Verify and Repair transaction 2014-06-27 14:33:07, Info CSI 000001db [SR] Cannot repair member file [l:34{17}]"Magnification.dll" of Microsoft-Windows-Magnification, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2014-06-27 14:33:07, Info CSI 000001dd [SR] Cannot repair member file [l:34{17}]"Magnification.dll" of Microsoft-Windows-Magnification, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2014-06-27 14:33:07, Info CSI 000001de [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery" 2014-06-27 14:33:07, Info CSI 000001e1 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:34{17}]"Magnification.dll"; source file in store is also corrupted 2014-06-27 14:33:07, Info CSI 000001e3 [SR] Repair complete
I've uploaded a file - tptaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\tptaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\tptaa
or
DIR E:\tptaa
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\tptaa <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Having difficulties - F8 not giving Advanced boot Menu. It's as if the USB Keyboard is not being powered up until after the option for F8 has passed. Going to try to find a old PS/2 keyboard
There may be an alternative - as soon as you start getting the Windows logo boot screen, turn off the power - this should trigger the option.
Neighbor had one - message in DOS box
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>
log included - trying to run update
same error 9c59
I was afraid of that - the c59 error appears to be a bit of a catch-all message (the same as a 643 error), and often means that finding a meaningful error-message is a long and possibly impossible process. - then you have to fix it!.
The simplest/quickest solution is usually a repair install (assuming that works).
Have a look at the instructions here... Repair Install
I'll pass on the rebuild, I'll just do without IE11, since I use FF as the browser of choice, it was just an annoyance that i was trying to fix - Thanks for trying