Great! - it seems to have been purely some corruption in the output, rather than the actual files themselves.
This obviously then bring up the question of why your system is different to everyone else's on the planet :)
The CheckSUR report is now clear, so go ahead and try installing IE 10 first.
Now works perfectly.Internet explorer installed.:)
Would you be so kind of explain why the first 2 times the fix don't have worked.
The files I had taken from another windows 7 64 bit.
what it meansit seems to have been purely some corruption in the output, rather than the actual files
Thanks a lot
Your reports show variations in the output -
Code:(f) CBS MUM Corrupt 0x00000000 servicing\*Packages\*Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file nameWhereas they should be simply...Code:(f) CBS MUM Corrupt 0x00000000 servicing\%shy;Packages\%shy;Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
I'm struggling to work out how that could happen.Code:f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
Quote