New
#51
Software errors maybe but if mechanical parts or controller electronics are a problem, no SW can repair that.
Software errors maybe but if mechanical parts or controller electronics are a problem, no SW can repair that.
With conventional drives, suffering this issue due to the latest TP version, there are a lot of people stating that accessing the drive is possible via a Linux Live CD, and indeed some have stated that the mere action of accessing this way can reset the drive to a working state.
This may be something to try if all other methods fail
As I said here on or in another thread. I think the cause is the partition overlapping whether the partition is mbr or gpt. I think this is what causing boot issues. It would be interesting to know if it does this when windows 7 is installed on a partition without the system reserve partition or with windows having a system reserve partition. This may explain why it doesn't work on some Vm's setup as well. Does the system reserve partition need to be bigger or is the build overlapping partition when it shouldn't.
Another possible thing, is the active partition got set wrong during install this will also cause boot errors and can be set back using diskpart from the installation disk.
Last edited by groze; 26 Nov 2014 at 13:34.
Yea 10 made shambles of the 7 boot manager Twice nothing fixed but a clean install so there might be a difference in installs without the system reserved partition ?
Cheers.
On another note,
Accidently I noticed 10 can access 7's system but 7 can not access 10's system,
I got a you do not have permissions to access :/
Good tip,
You may have missed the point,
7 can not make changes to 10 is my interpretation of the built in install of 10 meaning 10 is a restrictive alpha,
Cheers.