I went six months stalling updates, and then one day I couldn't connect to the internet. Checked the wifi driver and it was disabled. Re-enabled it and it was instantly disabled again. After updating it worked.
Passive aggressive little shits. Always hated Win10, but once support is up, it's back to Linux full time.
try checking the fucking time on the pc for a start. 9 out of 10 whines about 'hurr winduz wont do internetz' is somehow the system clock has desynced and the time is out by an hour, it breaks connectivity.
the other issue i had was between ISPs shutting you off entirely in a way that fucks with your home network, and 'local' network apps that still magically require an internet connection, so for some magical reason that has fuck all to do with microshit and everything to do with some other cunt forcing an update on me, i cant communicate between two local pcs because 'cannot connect to server'
tl'dr try basic fault finding. and not microsofts 'switch it off and on again, update all drivers, spin around 5 times and sacrifice a chicken to molock' type cut and paste responses, actual 'oh you fucking idiot' kind of fault finding. like checking the fucking time is correct. or the fucking shit i do to myself every time i cant print anything... because i set the print spooler to manual trigger and forgot - same goes with updates, not only can you completely stop the updates, you can actually create rules to download specific updates but no forced shit, AND, right, AND, you can disable the background processes that keep on firing off triggers to re-enable the update shit.
Yeah, neither had I until I watched the device disable itself in real time under Device Manager. Reinstalling the driver did not work. Update and restart magically let it stay enabled.
Why did it do that? No idea, but Occam's Razor says it was probably Microsoft. Non Windows devices were connecting just fine.
not only can you completely stop the updates, you can actually create rules to download specific updates but no forced shit, AND, right, AND, you can disable the background processes that keep on firing off triggers to re-enable the update shit.
this shits all over the internet.
Well aware, but I did not do that on that machine and would simply just force shutdowns without update. Not like it matters trying to explain this to you, because you're obviously a guy who thinks everyone but yourself is a retard and will reply with "PEBKAC" over inexplicable issues.
[ + ] MuricaPersonified
[ - ] MuricaPersonified 5 points 8 monthsAug 9, 2024 16:04:27 ago (+5/-0)
Passive aggressive little shits. Always hated Win10, but once support is up, it's back to Linux full time.
[ + ] Trope
[ - ] Trope 0 points 8 monthsAug 9, 2024 23:46:22 ago (+0/-0)
[ + ] observation1
[ - ] observation1 0 points 8 monthsAug 10, 2024 01:17:35 ago (+0/-0)
[ + ] i_scream_trucks
[ - ] i_scream_trucks 0 points 8 monthsAug 10, 2024 00:01:45 ago (+0/-0)
try checking the fucking time on the pc for a start. 9 out of 10 whines about 'hurr winduz wont do internetz' is somehow the system clock has desynced and the time is out by an hour, it breaks connectivity.
the other issue i had was between ISPs shutting you off entirely in a way that fucks with your home network, and 'local' network apps that still magically require an internet connection, so for some magical reason that has fuck all to do with microshit and everything to do with some other cunt forcing an update on me, i cant communicate between two local pcs because 'cannot connect to server'
tl'dr try basic fault finding. and not microsofts 'switch it off and on again, update all drivers, spin around 5 times and sacrifice a chicken to molock' type cut and paste responses, actual 'oh you fucking idiot' kind of fault finding. like checking the fucking time is correct. or the fucking shit i do to myself every time i cant print anything... because i set the print spooler to manual trigger and forgot - same goes with updates, not only can you completely stop the updates, you can actually create rules to download specific updates but no forced shit, AND, right, AND, you can disable the background processes that keep on firing off triggers to re-enable the update shit.
this shits all over the internet.
[ + ] MuricaPersonified
[ - ] MuricaPersonified 0 points 8 monthsAug 10, 2024 07:10:19 ago (+0/-0)*
Yeah, neither had I until I watched the device disable itself in real time under Device Manager. Reinstalling the driver did not work. Update and restart magically let it stay enabled.
Why did it do that? No idea, but Occam's Razor says it was probably Microsoft. Non Windows devices were connecting just fine.
Well aware, but I did not do that on that machine and would simply just force shutdowns without update. Not like it matters trying to explain this to you, because you're obviously a guy who thinks everyone but yourself is a retard and will reply with "PEBKAC" over inexplicable issues.
[ + ] anon
[ - ] anon 3689160 [op] -1 points 8 monthsAug 9, 2024 17:01:36 ago (+0/-1)
[ + ] anon
[ - ] anon 3992143 1 point 8 monthsAug 9, 2024 17:13:32 ago (+1/-0)
[ + ] anon
[ - ] anon 2597331 1 point 8 monthsAug 9, 2024 17:44:00 ago (+1/-0)
[ + ]anon
[ - ] anon 3152333 0 points 8 monthsAug 9, 2024 22:55:28 ago (+0/-0)
[ + ]anon
[ - ] anon 1735121 0 points 8 monthsAug 9, 2024 17:13:53 ago (+0/-0)
[ + ] MrPancake
[ - ] MrPancake 0 points 8 monthsAug 9, 2024 17:08:14 ago (+0/-0)