Back in the Windows XP days, there was a way of halting forced updates by killing a certain process. I had it as a simple batch file on my desktop. Every time it would come up with "your PC gets restarted in 15 minutes", I'd just double click on it and carry on undisturbed.
.NET on Linux – bye, Windows 10
111–120 of 290 posts
Re: .NET on Linux – bye, Windows 10
#112Earlier quoted context omitted.
In Win 10 Anniversary Update you can specify active hours, when you use the device and it shall not be rebooted. Also, there's a setting for custom restart time. http://betanews.com/2016/06/09/control-when-windows-10-insta...
I found out the hard way that you may only specify up to 12 hours as active, in one period. So, if like me, you use the computer in the morning and again in the evening, you are SOL.
You can reschedule the reboot if it hits during your working hours beyond that period (second part of the article under the link shows the UI).
Re: .NET on Linux – bye, Windows 10
#113Back in the Windows XP days, there was a way of halting forced updates by killing a certain process. I had it as a simple batch file on my desktop. Every time it would come up with "your PC gets restarted in 15 minutes", I'd just double click on it and carry on undisturbed.
Was that really necessary? As far as I remember, XP let you choose to not install updates automatically.
Re: .NET on Linux – bye, Windows 10
#114The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.
In Task Scheduler, expand the Task Scheduler tree to go to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator -> Disable Reboot task In the folder %Windows%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator remove write permissions for all users from the reboot file. https://techjourney.net/permanently-disable-prevent-automati...
Don't forget to do it again after any updates because MS will likely "fix" the obvious mistake you just made.
Re: .NET on Linux – bye, Windows 10
#115Windows 10 is a clusterfuck of an OS. Installed it on my dad’s PC, a simple machine with browsing software and a few arcade games. Didn’t go with the full install, instead did an upgrade from Win7. Everything was honky dory until it downloaded a ginormous 1GB update. The update failed and now every time he shuts down the update tries to install again. It takes north of five minutes to shut down. Install, fail, rollba…
The most sad thing for me is how Windows is such a given for PC gaming. :( It wouldn't have to be like this, there's nothing saying it should be a huge gaming OS, so it's too bad it is. I wish Valve would have been more successful with Steam OS. That would have fixed everything at least for me. As someone who otherwise likes amateur photography and programming, Linux is just as good or better at everything else with…
> I wish Valve would have been more successful with Steam OS
I think Valve has done an outstanding job, unfortunately, other game studios and controller manufacturers don't seem to care.
For example Logitech gaming wheels don't support linux. Although there are pretty good reverse engineered drivers, last time I tried, force feedback support was hard to get configured and didn't work as well in games such as Euro Truck and American Truck, which have linux versions.
Now, like the OP, I had encounters with windows 10 forced updates: I stream on twitch and I recall at least one time where, from my viewers point of view, my stream abruptly terminated. Turns out Windows 10 decided to update itself locking my computer for at least 1 hr.
Re: .NET on Linux – bye, Windows 10
#116Earlier quoted context omitted.
You mean pulling the plug instead of shutting down normally? I suppose that'd work but usually you only realize that Windows wants to update _after_ you hit the shutdown button. And powering the machine down in this state will likely result in an unbootable machine. And good luck fixing that, especially if your hard-drive is encrypted.
Windows updates fall into various categories in how they are deployed (this also causes variations in whether you need a restart or not). The overwhelming vast majority of updates nowadays are deployed in a rather safe mode where nothing on the system is changed during install until at the very end effectively a switch is made to the newly-deployed components. Those updates tend to not care very much, or at all, abou…
True, but that doesn't really help you, does it. There is no indication on the screen which kind of update is currently being deployed. So shutting down your machine is still a gamble, something you definitely don't want on a production machine.
To use a car analogy: modern car's safety measures would probably protect me in case of an accident, but there is no way of being sure. So I'd rather avoid crashing into things at great cost.
Re: .NET on Linux – bye, Windows 10
#117Earlier quoted context omitted.
It's really not too bad with root. Although the permissions and selinux stuff will trip you up a lot.
Yes, but those aren't the devices normal users get on the store.
Yes they are. However the rooting process isn't something normal people do with their normal devices.
Re: .NET on Linux – bye, Windows 10
#118> Before I did manage to install a fresh system on my laptop I had to disable UEFI, create valid partitions with special flags etc. it took me a while to figure this out, yet it wasn’t that difficult. Ha, right here is why "the year of the Linux desktop" will never happen. It's basically a kit car. Some people may find it "not that difficult" to weld a chassis together and rebuild an engine, but it's never going to b…
I wonder what he fucked up to make this necessary. Modern Linux distributions work fine with UEFI and create the necessary EFI System Partition itself.
His UEFI might have "secure boot" locked. I've heard that's an issue with some laptops.
Obligatory Wikipedia reference: https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_In...
Re: .NET on Linux – bye, Windows 10
#119Earlier quoted context omitted.
WHY is it just a Ubuntu release and no RPM? I really HATE when developers go Ubuntu = Linux
I don't think that's their responsibility. Traditionally it's your distribution's job to create and provide packages. Arch Linux has one (I just installed it myself) and if we're talking rpm: Fedora has one as well, it seems [1]. So, what is upsetting you here, really? 1: https://admin.fedoraproject.org/pkgdb/packages/pinta%2A/
> Traditionally it's your distribution's job to create and provide packages
That has not been true in my 15 years of Linux. Look at bitsync, rstudio, or other major programs. Arch Linux must build off of the source so that isn't a fair comparison you are on a totally different system (port).
EDIT: Here is the one page of documentation to push out deba nd rpm on mono projects. http://www.mono-project.com/docs/getting-started/install/lin...
I have seen electron applications (pinta isn't built on electron but mono) and in the same way ONLY Ubuntu is advertised under Linux. The ability to automatically build Linux formats is built into the framework and still don't add RPM.
Linux: AppImage, deb, rpm, freebsd, pacman, p5p, apk.
Still other eclectron applications do the same thing and ONLY provide Ubuntu and not provide the Deb or RPM with source.
Look at the download page it says Linux and directly under it has a Ubuntu Logo and a ppa link. When I down load any of my commercial or major software there is always a RPM and a DEB with a tar.
Linux Support = RPM (The official Linux Foundation package) DEB and Source.
I use OpenSUSE and they have awesome build service that allows people to build packages for SUSE but also RPM, Arch and anyone else you want to add.
Re: .NET on Linux – bye, Windows 10
#120Earlier quoted context omitted.
In Task Scheduler, expand the Task Scheduler tree to go to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator -> Disable Reboot task In the folder %Windows%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator remove write permissions for all users from the reboot file. https://techjourney.net/permanently-disable-prevent-automati...
Don't forget to do it again after any updates because MS will likely "fix" the obvious mistake you just made.
Check point 6 of the linked article.