New
#11
Perhaps respond to what has been already asked for?
- Disk Management - Post a Screen Capture Image
- try to boot with a Windows 7 Repair Disk instead or if you have a installation USB/DVD.
"Windows not genuine" 0x8004fe21, possibly problem with sppcext.dll
-
-
New #12
Here:- Disk Management - Post a Screen Capture Image
Not sure what to do here - I can boot with a repair disk, but selecting "startup repair" just restarts like normal and System Restore doesn't fix the problem. Should I try Memory Diagnostics?- try to boot with a Windows 7 Repair Disk instead or if you have a installation USB/DVD.
-
New #13
There is an option to start command prompt in recovery options. Just make sure to use the correct drive letter (your Windows partition will most likely be called E)
-
New #14
So I managed to launch a command prompt from the repair disc, but when I tried to follow NoelDP's instructions to copy the contents of dddaaa, it refused to navigate to the folder, I got "file not found."
-
New #15
Are you sure you are running the command for the correct drive letter?
Which partition give you a list of folder contents?
DIR C:\dddaa
DIR D:\dddaa
DIR E:\dddaa
-
New #16
Pretty sure - it's on the C drive, and DIR C:\dddaaa gave me a list of folder contents.Are you sure you are running the command for the correct drive letter?
Which partition give you a list of folder contents?
DIR C:\dddaa
DIR D:\dddaa
DIR E:\dddaa
-
New #17
I think I see what may be happening.
When you boot to the Repair Environment, the system is booting instead to/through the Recovery partition or the 'OEM partition' - which is marked as read-only. It seems to be a bit of a bodge-job on someone's part in terms of the partitioning.
The best way around it is to boot using either a Repair disk, or a full System disk - the Dell Recovery disk should work for this if you have it handy?
Once you're in the Repair Environment, you MUST do the DIR there - I can pretty much guaranteed that the proper drive letter will actually be D: (although it may be E: depending on how the OEM partition is tagged in the MBR)
-
New #18
Sorry for the delayed reply - just moved house so only just got round to trying this again now, and thankfully it worked! Not sure what I did wrong last time, but this time booting into the recovery environment, running dir c:/dddaa and then xcopy-ing it worked perfectly. Successfully ran an sfc scan and haven't been harassed by any errors. Thanks all!!
Quote
Related Discussions