Switched around hard drives and now I have several gig's missing.

[MR.Clay]

so basically i was trying to upgrade form z270 to z390(i5 6600k to a i5 9600k) (6 core yay!)and it turned into a complete cluster fuck of a posses that eventually failed. I dident know that z390 will not support windows 7(thanks Microsoft).  Anyway in the defeat and realization i began to switch out the motherboard form the new one back to the old one. And boot back to windows 7, but that dident go over so well. It wouldn't boot back into windows but just the bios. So i went in and did some "reconfiguration" i have no idea what i did. But know i have a drive that i called the "VALT" as a kinda mass storage solution for youtube clips. And when i booted back up into windows it wasn't their! CODE RED BOY'S. And so here I'am , please help this scrub lord. 

[Ashley MLP Fangirl]

you have absolutely no idea what you changed in the bios?

[Bruno_A]

I don't think you can simply take out a drive with Windows 7 installed on it, and plug it into a whole different machine, or platform, because of the Windows 7 drivers. With Windows 10, you can, even though you probably should reinstall anyway. Please correct me if I'm wrong, anyone.

[King_Jahh]

21 minutes ago, bruny06 said:

I don't think you can simply take out a drive with Windows 7 installed on it, and plug it into a whole different machine, or platform, because of the Windows 7 drivers. With Windows 10, you can, even though you probably should reinstall anyway. Please correct me if I'm wrong, anyone.

No you're right.

 

A drive with windows 10 can be plugged into basically any other PC and it will just install new devices drivers and sort itself out. It's a bit messy and can create some weird bugs sometimes but it works. Not as nice as a clean install obviously.

 

But windows 7? Nada, that OS would've basically crippled itself trying to do that.

 

If you have another working PC somewhere, plug the drive into that (externally, don't boot of it lol) and see what files you can pull from it... But yeah, you likely gonna need a fresh install mate

[MR.Clay]

Mable i didn't configure the "Valt" drive in the bios and that's why its not showing up? It's a WD blue drive. 2.tb And bye the way thank's for the fast reply's guy holy shit LIKE who needs to pay for tech support when you have you guys.  

[MR.Clay]

I have Asus maximums gene III mirco atx motherboard. btw. im see what i can do in the bios. Let me know if their is anything that i should be worried about as far as bios stuff. I haven't done this in a long time so im kinda rusty. 

[MR.Clay]

So i have 3 drives the c /.drive, the v /.drive(the one that wont show up) and the m.2 ssd i have installed in the motherboard. So the V/. drive is now showing up as the a D/. And thier's no folders on it, it's as if been completely wiped. Please for the love of god don't tell me that this stunt wiped the V./ drive. Would thier be any way to recover the files? Or am i completely fucked?

[MR.Clay]

so basically i dident have the sata port connected in the right spot on the motherboard. opps....

Well.... thats embarrassing. So I have got everything up and running now including the lost files. Yay. And a new 4th drive that i'am using to move everything form the (C:) drive to the new (Q:) drive (blank, 2.tb drive) Western digital Black. Enterprise grade baby! So thank's to all the "helped" me. More like helped keep my sanity. 

[Roswell]

1 hour ago, MR.Clay said:

so basically i dident have the sata port connected in the right spot on the motherboard. opps....

Well.... thats embarrassing. So I have got everything up and running now including the lost files. Yay. And a new 4th drive that i'am using to move everything form the (C:) drive to the new (Q:) drive (blank, 2.tb drive) Western digital Black. Enterprise grade baby! So thank's to all the "helped" me. More like helped keep my sanity. 

It's time to move on to Windows 10 anyway. In 3 months, Windows 7 will lose support from Microsoft and be an enormous security risk, not to mention most software developers will stop supporting it in like fashion.

 

If you're holding back from Windows 10 because of telemetry, Windows 7 already has it. It was backported years ago.

[homeap5]

6 hours ago, bruny06 said:

I don't think you can simply take out a drive with Windows 7 installed on it, and plug it into a whole different machine, or platform, because of the Windows 7 drivers. With Windows 10, you can, even though you probably should reinstall anyway. Please correct me if I'm wrong, anyone.

You're wrong. I made that lot of times. It may sometimes be tricky and once or twice I must used Paragon Adaptive Restore to adjust os to new hardware, but in 90% of cases everything works. Even switched from core2quad to Ryzen 5 1600. Of course that change needs some adjustments sometimes, but it's still faster than reinstalling everything (depends on what someone has installed - for people who has only few games and internet browser, reinstalling system may be the same fast).

 

Too many people says that "no, it can't be done", but almost everyone repeats that after other guys without check.

 

About that end of win7 support - so what? I'm using still one computer with win XP in my work and have no problem. System installation date was about 12 years ago, meanwhile motherboard was changed, drive was changed to ssd (cloning) and the same system still works. I'm still waiting for that thousand of hackers that supposed to attack my XP. Unfortunatelly, like y2k problem, it never happend.

 

If we're talking about computers, I think one of main problem with computer users is that they're afraid of unspecified problems, theoretical problems etc. Like "I strongly recommend reinstall Win10 if you're changing component xxx". Why? Oh, SOMETHING may be wrong and you may have SOME problems. I really hope I never meet any home repair crew that think similar - they'll probably suggest that I should buy again my own flat, take out all furnitures and bring them back. Just in case, because I bought new speakers and it's better to set everything again.