Windows 10: Recovery disk / Hide disk problem

So far everything was okay, but for some reason the IRST ( Intel rapid storage technology ) came up on a daily basis some upgrade or refresh. I enabled. Disappeared from drive D. Disk management can not see it. I've been trying everything, I gave up. Please, help. ( Acer Predator G9-593 ) Operation system win 10.



:)

 

XP disk versus Laptop Recovery Disk?

Recovery disks are just OEM copies of XP disks. Ie, they can have things such as the companys logo within the files.

If you got a normal XP disk you cant use it. The only way your dads copy of XP will activate is if your normal XP copy is OEM, unless you use the recovery disk.

I always use the recovery disks. Works just like a normal copy *Smile . Plus with the recovery disks you dont need the serial key as I *think* its embedded into the files on the disk. Just need to activate windows once on the net *Wink .

 

XP disk versus Laptop Recovery Disk?

My dad wants me to do a clean reinstall of Windows on his laptop.
Through SIW I know his windows code and so I can install xp off one of my disks and use his legit code.
He also has a 'recovery disk' for his laptop, but I've got no experience with recovery disks and don't know what they contain... is it a normal XP?

Would it be best for me to reinstall using the normal XP diskette?

 

Disk management console view is not up-to-date

i dont know how to fix your disk management, but i can fix your partition problems...




open up Command Prompt with admin rights. (Right click, run as admin)


enter in
DISKPART
list disk

then find the Disk number for your Raid array... lets call it number 7 ( you can tell what disk is what by the total size)
type in

Select Disk 7
List Partition (will give you a list of all the partitions..)
Select Partition 1 (im assuming you only have 1 partition on Disk 7) repeat this step if you have more partitions.
ASSIGN


that should get the array up and running ready to use.


EDITED.

any problems, post back ^^


Still EDITING *Stick Out Tongue

side question, have you tried restarting the PC?