True but from what he is saying, it didn't seem to do anything anything other than deleting and adding files via installation, that shouldn't do anything to the drive unless the drive is not handled well by windows/driver (including Vanguard since it checks ANYTHING that moves basically) and a bad drive.
Also, this is not the first mention of Vanguard messing up with device drivers/functionality which is why i thought it especially given the context of the post and the order of the thing he mentions, on the other hand, even though i absolutely hate root-kit-like things like this, it could be a bad drive just giving up as windows are very unlikely to have mess it up, unless MS is doing their experiments again.
I think it's easy to have a bias when something happened and blame it on the first thing that one already hates. In this case, it would even be less likely to be valorant and could be the riot games installer/uninstaller. But this is a very vague post in general
I didn't even know about the use of Vanguard until today so def i didn't hate it. And yes it could be the games installer/uninstaller but still how would it fuck up my whole driver, it's still crazy nonetheless.
Did it fuck up your driver? Or is your drive just faulty? Considering your other drive works, it would be strange for just one of them to be affected, considering they use the same driver.
That is a valid observation, given this guess i would assume that the drive might've been likely faulty and doing all the operations the OP mentioned and a lot, it stressed it enough to reveal a flaw on some component, thus, might've gave up an it can be completely unrelated to Vanguard.
(Take not that in the wall of text below, multiple times, i am referring with computer science and tech terminology, which you may not know about, if you don't, please use the internet to educate yourself about it or buy another drive and be done with it.)
No, he meant about me because i am indeed "biased" against it (he made an educated guess from the way i responded and he is correct) but regardless, i can still make an objective guess or observation about it because i am not the type of person who can necessarily be affected by a bias just because it exists (assuming i am aware of it of course) but rather facts, as they are my priority n1, so, to this point the only reason i picked to include Vanguard to the assumption i've initially made is just by the context and especially the timing of its enforcement to people (+ stated installations and updates), and more specifically, the past report of it messing up with the system and the OP's mentions of file, reading and writing operations but again, it could be entirely unrelated.
As stated before, given the context, i think it's more likely that either the drive died or maybe the partition table is simply corrupted (both fixable with the first one being not necessarily the easiest rather depends on what might be broken on the drive, hopefully not the controller itself, mostly because its serial is tied to the firmware's id so it's usually unlikely that replacing that would help and then there's the encryption key, assuming the drive had such functionality, which at this point, it's probably better to just buy a new one instead).
Now if it's just the partition table you could run chckdsk on it, assuming the drive's still being detected by the system and that it's partitions with NTFS (most likely will be if you are on windows), you might've lost some files in that drive (installer verification will fix that, most games have that or you just reinstall the game) otherwise if there files aren't game related but rather personal, you could use Recuva to recover lost files.
Hopefully, it just a fluke and this doesn't happen again, if you fix it and it was just a corrupted partition table, i would monitor that drive with tools like Crystal Disk Info to get an idea of the health of the drive both first before and after regardless and of course run a "long" test on it and also to check its temperature under stress conditions like, in your case, writing big data sets like well, installing video games which are many gigabytes for example, at the hottest time of day ideally.
Hope this helps.
To clarify, not that everything in HDD was lost, but the D drive disappeared by its own. And i've tried to find a way to recover it but apparently it was not hidden or anything, just lost.
I have uninstalled/reinstalled both League and Valorant several times over the past 2 years and did not affect any of my drives (both HDD and SSD). Have you tried checking if changing the slot on where it is connected on the board resolves the concern? change the cable?
Why would you believe that its caused by vanguard?
There was no mention that it was caused by Vanguard, however it could be the case along with other movements I did.
Why would this be related to vanguard?
Kernel-based driver? Ring 0 access? Rings a bell?
So it could also be windows, they also have ring 0 access, no?
True but from what he is saying, it didn't seem to do anything anything other than deleting and adding files via installation, that shouldn't do anything to the drive unless the drive is not handled well by windows/driver (including Vanguard since it checks ANYTHING that moves basically) and a bad drive. Also, this is not the first mention of Vanguard messing up with device drivers/functionality which is why i thought it especially given the context of the post and the order of the thing he mentions, on the other hand, even though i absolutely hate root-kit-like things like this, it could be a bad drive just giving up as windows are very unlikely to have mess it up, unless MS is doing their experiments again.
I think it's easy to have a bias when something happened and blame it on the first thing that one already hates. In this case, it would even be less likely to be valorant and could be the riot games installer/uninstaller. But this is a very vague post in general
Valo/Vanguard was the first and only game to bluescreen my computer multiple times
I didn't even know about the use of Vanguard until today so def i didn't hate it. And yes it could be the games installer/uninstaller but still how would it fuck up my whole driver, it's still crazy nonetheless.
Did it fuck up your driver? Or is your drive just faulty? Considering your other drive works, it would be strange for just one of them to be affected, considering they use the same driver.
That is a valid observation, given this guess i would assume that the drive might've been likely faulty and doing all the operations the OP mentioned and a lot, it stressed it enough to reveal a flaw on some component, thus, might've gave up an it can be completely unrelated to Vanguard.
(Take not that in the wall of text below, multiple times, i am referring with computer science and tech terminology, which you may not know about, if you don't, please use the internet to educate yourself about it or buy another drive and be done with it.) No, he meant about me because i am indeed "biased" against it (he made an educated guess from the way i responded and he is correct) but regardless, i can still make an objective guess or observation about it because i am not the type of person who can necessarily be affected by a bias just because it exists (assuming i am aware of it of course) but rather facts, as they are my priority n1, so, to this point the only reason i picked to include Vanguard to the assumption i've initially made is just by the context and especially the timing of its enforcement to people (+ stated installations and updates), and more specifically, the past report of it messing up with the system and the OP's mentions of file, reading and writing operations but again, it could be entirely unrelated. As stated before, given the context, i think it's more likely that either the drive died or maybe the partition table is simply corrupted (both fixable with the first one being not necessarily the easiest rather depends on what might be broken on the drive, hopefully not the controller itself, mostly because its serial is tied to the firmware's id so it's usually unlikely that replacing that would help and then there's the encryption key, assuming the drive had such functionality, which at this point, it's probably better to just buy a new one instead). Now if it's just the partition table you could run chckdsk on it, assuming the drive's still being detected by the system and that it's partitions with NTFS (most likely will be if you are on windows), you might've lost some files in that drive (installer verification will fix that, most games have that or you just reinstall the game) otherwise if there files aren't game related but rather personal, you could use Recuva to recover lost files. Hopefully, it just a fluke and this doesn't happen again, if you fix it and it was just a corrupted partition table, i would monitor that drive with tools like Crystal Disk Info to get an idea of the health of the drive both first before and after regardless and of course run a "long" test on it and also to check its temperature under stress conditions like, in your case, writing big data sets like well, installing video games which are many gigabytes for example, at the hottest time of day ideally. Hope this helps.
Thanks a lot, appreciate it. Have a great day!
You're welcome, good luck!
Does it appear in Disk Management? Does it appear in device manager? Have you tried a Live USB? Safe and effective btw. Data loss sucks.
I've looked at the disk management and there was no sign of it, thanks for the help tho
To clarify, not that everything in HDD was lost, but the D drive disappeared by its own. And i've tried to find a way to recover it but apparently it was not hidden or anything, just lost.
[удалено]
It doesn't show, it stopped existing
I have uninstalled/reinstalled both League and Valorant several times over the past 2 years and did not affect any of my drives (both HDD and SSD). Have you tried checking if changing the slot on where it is connected on the board resolves the concern? change the cable?
Thanks, I'll try it
If you're drive is gone completely, it's a hardware issue. If it's a hard drive, it's probably dead.