windows update bricked my touchpad.
rebooting bricked my keyboards.
reinstalling windows fixed my keyboards but not my touchpad.

this has been going for a week now.
i'm moving back to linux. maybe i'll try arch this time around.

fuck you microsoft.

ps: my touchpad seems to be permanently bricked.

!dev

While I'm not all too great with developing things, still learning actually, I am good at breaking things unintentionally.

For instance, I fucked the YouTube app up so badly, even a force stop isn't fixing it.
Gonna try rebooting, see if that helps.

More network/hardware than dev but anyway: I use OPNsense as a firewall at home on an embedded system. Had everything set up nicely and appearing to be working fine, quite a lot of things set up (static leases, VLANs with various firewall rules etc. - a fair bit of stuff involved). I noticed my remote system was failing to back up to my local one. Turned out port forwarding wasn't fully working (initial packet got through but nothing else). I noticed this at midnight.

Ran an update to see if that helped - nope. Reboot time then! It made its shutdown noises and I waited 15 minutes before giving up (no noises, no ping response). Took SD card out. Copied a fresh install onto it, thus wiping all settings. Booted up fine, set up my internet connection, all good. Proceeded to configure it. Noticed I couldn't access the internet from my PC, but could from the firewall itself. Rebooted the firewall. It didn't come back up. Argh!

Reinstalled AGAIN. Attached a serial cable and it was complaining about something which sounded like it couldn't read the SD card. Tried another. Nope. Looked online (using phone): known issue to do with boot delays.

Gave up and went to bed at this point (4am).

Next day: Installed it in a VM instead. Still no internet from my PC! Another known issue to do with default gateway not being the PPPoE interface. Got into shell, manually changed the default route. Was then able to update to the latest version which fixes the gateway issue. Rebooted the VM. All good.

Put all my settings back in, this time taking a backup afterward.

Only to discover....

....port forwarding wasn't working properly. Back to square 1.

Poked around with some NAT settings (outbound ones), made no difference, undid those changes and suddenly it started working.

WTF? /waves arms in the air

OPNsense folk were very helpful, producing a new build for me to try within a couple of hours of me asking about the problem.

But days like that, I start to question whether I really enjoy technology as much as I thought I did...

I just fucked up real bad:

My phone was giving some error about not being able to install an update. Fair enough, i think to myself, so i try rebooting. Still nothing...

I then remember that i at some point OEM unlocked it for some testing, so i start up adb and see if i can connect during the update process. I can't. This is bad: I can't get into my home environment, nor can i connect with adb

Then i try booting into recovery, but instead of booting to ACTUAL recovery, it boots to some custom made "E-Recovery" made by huawei (my phone is a huawei p9 lite), which only gives me the option to download the update, which crashes, and no way of resetting. However, from here, i am finally able to connect to my internal storage via hisuite to make a backup

Next up: Bootloader
So i next load up the unlocked bootloader to try and manually flash the update. That works great, but it still wont boot normally. So i figure: it must think my device is in fact a different device. At this point i'm pretty fucked: Even though i have my data backed up, i can't manually download the update from huawei's site because i don't have the right keys, and i can't download an OTA because their site sucks and half of the downloads don't work, including the one i need. So now i'm stuck here with a bricked phone because EMUI doesn't know how to install an update.

I then did the stupidest thing i have done to date: i wanted to flash a custom recovery image over the "E-Recovery" in order to do some troubleshooting, but instead of writing
"fastboot (mydeviceid) flash recovery recovery.img"
I wrote
"fastboot (mydeviceid) flash boot recovery.img"
Meaning i flashed my BOOT partition with a custom recovery image that turned out to not be able to run. Great! Now i've totally fucked my boot sequence

I can't call their support line either, because as soon as they realize i've tried to restore it myself, and therefor had my OEM unlocked, they basically just hang up.

Can we just for a moment recognize how absolutely fucked Windows update is?

I have done everything, EVERYTHING, outside of booting from a live Linux OS and permanently deleting the windows update executables. All this to stop windows from force updating and rebooting my system while it's locked.

I've killed services, schedules, edited the registry, changed group policy. I even set my wireless connection as metered. Fun fact about that, if MS deems the update to be "priority" they'll download it anyway and reboot, so fuck your data-cap.

I wouldn't have a problem with it IF they would put everything back the way it was before, but those fucking cucks can't even be bothered with doing that. But you bet your fucking sassy ass they start up all the bullshit services I disabled last update are all running.

I don't even know WHY I even try.

Doesn't matter anyway, in a few months I won't even be able to use half the tools I use on Windows for work due to licensing issues 🤷‍♂️

At that point I will give a big fucking finger to Windows 🖕 and use a VM for all the fucking work related bullshit.

Fuck you Microsoft, I would say it's been fun but you're a god damned disaster. I wish that I could send a message to the entire MS board on how much they have failed, but unfortunately I rather like my freedom and it's frowned upon sending rotting roadkill in the mail.

I was having issues with PulseAudio on Ubuntu not working properly and spent about 40 minutes trying to modify various config files to fix the problem. Eventually, I fuck my system up so bad that there is no audio at all and PulseAudio refuses to even start. So I revert all of the config files to their original state and try starting PulseAudio, it still refuses even start. Then I try rebooting the system, and not only does PulseAudio work when I log back in but my original issues were gone even though I reverted all of the configs. Computers. How do they work? Nobody knows. But at least now I can listen to my music in peace.

Let me tell you about my wonderful weekend. It all started with a game that doesn't run in wine and it ended up in the biggest nightmare of Windows Update and EFI configuration.
1 - let's boot on my Windows partition to play trackmania 2.
2 - Windows Update interrupts me while driving a track.
3 - Update keep failing over and over again.
4 - I keep trying things to fix Windows Update, but with no success.
5 - Let's try system restore, failed
6 - Let's try to do a reset. "You don't have a recovery drive". Oh, right...
7 - Let's try to upgrade Windows 10 to Windows 10, just because. Nope, "we could not determine if your pc can run Windows 10". Wait what....
8 - I guess I'll be reinstalling this trash. "Nope, can't. Don't like that partition I just formatted". Of course you can't...
9 - Had to delete the partition and let it create new ones. It created a new EFI partition. Just why???
10 - Okay that worked. Let's fix grub now.
11 - Maybe not, let's try rEFInd, because it looks fancy.
12 - After rebooting on the live USB for about 50 times and reconfiguring rEFInd without any luck, I realised the install script didn't install fs drivers for ext4. Oh, right... That's why you didn't find any Linux kernel...
13 - It can't boot windows, they're using a different EFI partition. Let's move rEFInd to the new EFI partition windows created for me.
14 - Finally everything works again. So much effort to play a freaking game without being bothered by windows update. And rEFInd abience theme looks beautiful.

I've got to say though, I learned a lot and the Arch wiki is awesome!

Okay new Rant
INSERT TRIGGER WARNING HERE

OSX still sucks I have been using the bloody darn thing for last 8 months still I found things that are obnoxiously trivial missing.
Latest incident I was trying to plug in my android phone(soft bricked) in recovery mode and I had to push a file with ADB (i save this mutherfuker for another day). So back to the original topic now I plug it in and but turns out it doesn't recognize my device now as a preliminary check I decide to check my USB cable and my DONGLE both seem to be working fine now I try rebooting back into recovery. Now after scrapping the internet for a few hours I find that this problem is caused because sometimes due to a recurrent bug in OSX the operating system sometimes fails to recognize the difference in between directories "Adam"(just an example) and "adam" which in turn can interfere with some of the flags used while checking if a device might be connected.

I mean this is fucked why the fuck can you not simply use your device as an external storage that would have made the process easier by a fucking lot.

I think the people at Apple are going the destroy a UNIX powerhouse just to make their OS more CUPCAKE friendly.
And all of this is in addition to the problems with AFS.

I just wish I had not bought mac for development