Customer care guys are stupid
Me : yeah, OS crashed. It keeps getting into bios setup saying there's no hard drive detected on this system and no recovery file found as well, what do ?
Him : "well sir, your OS has been corrupted and now you have to buy new licensed one, if you can just give me your location I can help you locate out nearest service centre which will help you install a new licensed instantly"
Me : *WHAT THE ACTUAL TRIPLE FUCK* atleast try to understand the problem first.
Him : No need sir, I already come across this problem and now you have to pay, as I was saying *beep*
*I smashed the phone*
After that I fixed it myself
These low level shit licking faggots need to get themselves fucked in the ass by horses and then apply the same conversation when the intercourse begins with the horse.
Also, if I could be placed in the same customer care cell, I would do better.
So wk62 too I guess

i am BEYOND pissed at google.

as some of you know, i recently got android studio to run on a chromebook (you read that right), but it being a chromebook and google being a protective fucktard of their crappy operating system, i had to boot into bios every time i started it.

when i was with some friends, i started up the chromebook, and left, after telling my friends how to boot the chromebook.

ten seconds and literally one press of the esc button later, he broke the entire thing.

but that's not what that rant was about, i honestly knew it would happen eventually (although, this wasn't the best time).

so now this screen pops up.

"chrome os is damaged or missing, please insert a usb recovery drive" or something like that.

well, i'll create one. simple enough.

no wait, this is google, just your average 750 billion dollar company who cares more about responsive design then a product actually responding.

i started to create the recovery usb. of course, chrome developers thought it would be a good idea to convert the old, working fine, windows executable usb recoverer, and replace with with a fucking chrome extension.

i truly hope someone got fired.

so, after doing everything fine with the instructions, it got to the part where it wrote the os image to the usb. the writing stayed at 0%.

now this was a disk thing, writing os's and shit, so i didn't want to fuck it up. after waiting ten minutes, i pressed 'cancel.'

i tried again many times, looked things up, and frantically googled the error. i even tried the same search queries on bing, yahoo, duckduckgo and ecosia because i had the feeling google secretly had tracked me over the past 7 years and decided to not help me after all the times i said google was a fucker or something similar.

google is a fucker.

after that, i decided to fuck with it, even if it formats my fucking c drive.

i got to the same point where the writing got stuck at 0% and proceeded to fuck. i start spamming random keys, and guess what?

after i press enter, it started.

what the fuck google?
1000s of people read the article on how to make the recovery drive. why not tell them to press the goddamn enter key?

i swear there are hundreds of other people in my same situation. and all they have to do is press one fucking key???

maybe tell those people who tried to fix the shit product you sold them.

fuck you google.

Tried to dual boot Arch with Windows yesterday.

Everything was going smoothly. Shrunk the C: partition, ran the installer, installed the OS fine. But it was still booting straight to Windows.

So I edited the BCD to point to Grub instead of Wilndows. Then the plan was to boot into Arch, find Windows, and add it to Grub, problem solved.

Wrong. I had forgotten to disable secure boot. Arch and Grub were booting in BIOS mode, but Windows was UEFI. Grub couldn't boot or even see Windows.

So now I was stuck with just Arch. So I flashed a Windows drive, booted from that, automatic startup repair failed. Opened up the command prompt, tried to rebuild the BCD from there. Surely I can just rebuild it and forget about trying to dual boot right? I just want to get back to being able to use my PC.

Wrong again. Didn't find Windows. Had to get rid of the BCD file before I could rebuild it, but couldn't find it. Found out that I could use diskpart to mount the system partition and assign it a drive letter, renamed the BCD, rebuilt it, and finally was able to reboot into Windows.

Learn from my arrogance. First time Linux users should not attempt to install Arch, let alone do it alongside Windows on the same disk.

Stories like the one I'm about to tell you are just another reason why people hate Windows. I know I usually preach 'Don't hate everything' and shit, but this is a real big fucking deal when it hits your desktop for no reason.
Now, onto the actual story...

Background: Playing with my Oculus, fixing issues like forgetting to use USB3 and stuff. I learned about an issue with Nvidia GPUs, where in Windows, they can only support 4 simultaneous displays per GPU. I only have the one GPU in my system, Nova, so I have to unplug a monitor to get Oculus and its virtual window thingy working. Alright, friend gave me idea of using my old GPU to drive one of my lesser used monitors, my right one. Great idea I thought, I'll install it a bit later.

A bit later...

I plug the GPU in (after 3 tries of missing the PCI-E slot, fuckers) and for some reason I'm getting boot issues. It's booting to the wrong drive, sometimes it'll not even bother TRYING to boot, suddenly one of my hard drives isn't even being recognized in BIOS, fuck. Alright, is the GPU at least being recognized? Shit, it isn't. FUCKFUCKFUCK.

Oh wait. I just forgot the power cable Duh. Plug that in, same issues. Alright, now I have no idea. Try desperately to boot, but it just won't I start getting boot error 0xc000000f. Critical device not found. Alrighty then. Fuck my life, eh?

Remove the GPU, look around a bit while frantically trying to boot the system, and I notice an oddly bent SATA cable. I look at it and the bastard is FRAYED AT THE END! Fuck, that's my main SSD! I finally replace the SATA cable and boot, still the same error... Boot into a recovery environment, and guess what?

Windows has decided to change my boot partition, ya know, the FUCKING C: DRIVE, from NTFS to RAW format, stripping it of formatting! What the actual fuck Microsoft? You just took a shit on yourself while having a seizure on the fucking MOON! Fine, fuck you, I have recovery USB! Oh, shit, that won't boot... I have an old installation! Boot ITS recovery, try desperately to find a fix online... CHKDSK C: /F... alright, repairing, awesome! Repaired, I can see data, but not boot. So now I'm at the point where I'm waiting for a USB installer to be created over USB 2.0. Wheeeeeeeeee. FML.

THESE are the times I usually hate Windows a lot. And I do. But it gets MOST of my work done. Except when it does this.

I'm already pissed, so don't go into the comments and just hate on Windows completely. Just a little. The main post is for the main hate. Deal with it. And I know that someone is going to come at me "Ohhhhh, you need FUCKIN LIIIIIIINUUUUUUUXXXXXXXX!' Want to know my response to that?

No.

I got a new computer recently. I got it with an evo 970. I tried installing the Samsung controller software so that I can view the health of the drive.
No go. Why?
Looked around and everywhere they are saying turn off raid. I checked in bios. Says my drive is not in a raid volume.
Okay, now what?
Look at manual of laptop maker. Says there is a mode that allows you to use either VMD or RAID on the drive. Apparently I was in VMD mode. I had already backed up the computer at this point. Yes, I suspected this was coming. So I changed the mode.
No boot.
Okay, I have Aomei backup and linux boot disk I made using Aomei. Linux boot disk won't boot... Well fuck.
Luckily I have my old computer and a Windows 10 install disk. I install Windows 10 again, install Aomei and proceed to try and restore.
4 hours later... I dunno how long. I went to bed.
Wake up and test.
No boot.
I try disk repair.
No go.
So I boot into Windows 10 install disk to look at partitions. 5 or 6 fucking partitions. It has installed 3 partitions into the space of one.
Delete all the fucking partitions. Cause fuck you!
Okay, lets try this again.
I make a window pe boot disk this time.
It boots.
I do restore while I am at work.
I get home.
No boot.
Check partitions and find only 2. Better than last time.
I try disk repair.
No go.
Search the net. Literally: "Aomei restore no boot"
Someone says, just assign drive letter with drive C using diskpart.
Seriously?! Disk repair couldn't figure this shit out by context?
Seriously doubting this solution.
Solution works...

Now, I am an engineer/programmer/computer genius. I have been learning how to fix this shit for over 30 years.

How the fuck is Joe Bloe ever going to fix an issue like this? I feel sorry for the technically un-inclined. I honestly don't know how neither Aomei nor Microsoft cannot solve restoring disk images by setting a drive letter. How did this not get backed up by Aomei? How did this not get detected as one of the most common problems with a disk restore? Why has this been a problem with Aomei restore for over 3 years? I love Aomei. It works most of the time. But this is terrible. The tech world is definitely a shit show at this point in time.

I also read that VMD actually makes the communication to the drive a bunch faster. Not sure if the samsung drivers do the same. So there may be a tradeoff. Oh well. I can see the temperature of my drives now! Woot!

A weird thing happened when I tried to install linux mint on my PC.
Although I installed it on a hard drive (I have another hard drive for windows), my bios tells me that Linux would be on the same hard drive as Windows?? I can assure that it's not the case, as I plugged out the linux drive and grub couldn't boot Linux anymore, just windows. Plug back in, linux bootable. Ok fine?
When I installed linux I panicked for a moment, as I thought I had it correctly installed separately, instead it would have become a dual boot, according to the bios?

!rant
My home pc has developed a sudden issue and wont boot up anymore.

Stays stuck on the POST phase and am unable to get into BIOS , just stuck with a big asus logo and a message to press
F2 or Delete to get into BIOS but the system seems frozen as the keyboard lights are on but unresponsive while the
Mobo reads an error code A2
( the manual claims that to be an IDE error although am using only SATA)

Unplugging all usb doesnt change anything.

Unplugging all other sata ssd ,hdd and disk drives except the os drive changes nothing.

Unplugging the os drive results in the system complaining about no bootmgr
(As expected), that allows me to at least look at the BIOS but there doesnt seem to be anything wrong or out of the ordinary..

Booting from a live cd works fine

Booted from a pc boot repair tool and plugged in the os drive into one of the hot swappable sata ports shows me the all the files still there and accessible , check disk revealed nothing wrong. Can't plug in the os drive pre boot as that locks everything up again)

Tried to boot with a windows cd then do a start up repair but plugging in the os drive into the hot swappable sata doesn't work since windows can't see the drive.

Tried to swap the os drive with another one of exact same model filled witb random files resulted in no boot mgr error as expected

Struggled a whole weekend to fix it but alas no progress
Ah and the OS drive's warranty ran out 2 weeks ago 😑

Mobo asus p9x79 deluxe
Os ssd samsung 840 250 gb
No changes in hardware for the last year
Or so
No BIOS changes in over a year

I did notice some odd files like 0002Found
On the os drive when i was using the boot repair live cd tool, will bring the drive to
The office where i can get my hands on an ssd sata to usb caddy and take a snapshot of The files there for you guys to see.

Any ideas ? 😞