Saw this floating around😂😂

Windows 10, updating to version 1809.
That was only 3 months ago 🤷‍♂️

Preparing to install: 0%, 8%, 0%, 24%, 3%, 0%, 19%

I think I’m setting a restore point for this one 😣

So… I released v2.0.0 of devRant UWP a few weeks ago.
Then I got a lot of reports of problems on Windows 10 Mobile and older (than 1809) versions of Windows 10 on Desktop.
I decided to resubmit v2.0.0-beta16 to the store, and try to find the issue in the update… I didn't find it.
The code seems the same as the working version (at least the part I try to test is 100% equal).

So it seems I fucked up the vs project.

This means that to find the issue I can spend weeks to search it over and over inside the latest project (using shitty emulators of older Windows 10 builds to debug it), or I could just restore it to the old v2.0.0-beta16 (released in august) and implement again every single new feature and fix (something like 5 new features, dozens of improvements, changes and bug fixes).

In any case, this will require a lot of time (which I don't have at this moment).
I'm really sorry for this inconvenience, I know some of you use my client daily (~3.000 users I guess), I'm really glad someone likes it, and thanks a lot for the awesome reviews and feedback, but stable v2 (v2.1.0 at this point) will be available not earlier than in February.

Probably some of you have already download v2.0.0 while it was available in the store, and maybe it works on your device (please let me know in the comments below if you did, how is it going, and also if you like the new features and improvements).

After this epic fail, and more than 1 year (way too much) of v2 public beta, I want to throw the current project in the trash, and start it from scratch.
Which means I will start to work on v3 as soon as you will see v2.1.0 in the store, making it faster, lighter and with better support for the latest Windows 10 (Fluent Design and not) features, dropping the support for the very old UWP API.

Thanks for your attention.

Have a good day (or night)!

I don't know why I'm having this conversation so often lately.
Someone: "Hey, did you know that Microsoft said that Windows 10 would be the last version of Windows?"
Me: "Yes."
Someone: "But isn't that ridiculous? It would get old at some point, right?"
Me: "...have you heard of macOS X? It's also »the last version« of macOS. But it has still undergone a lot of changes."
Someone: "Hm... I haven't thought about that."

Seriously, just because a company says something would be the last version of a product, it doesn't mean they don't update it anymore, they just take that version, make it a brand and use a different number for versioning (macOS Mojave 10.14, Windows 10 1809, ...).

Companies really try confusing their users as much as possible, and it seems to work, because the convo mentioned above is just repeating so often at this point that it just has to be intentional confusion.

1809 is going to be my new PIN number.

Windows Update prompted me to install the 1809 update for Windows 10 recently.

I left the machine for a while and came back to find it frozen at a completely blank screen.

It eventually restarted...and got stuck in a continual loop where the Windows logo would flash for a second and then instantly restart again.

The restart occurred so early in the boot process that I couldn’t even get it into recovery mode or do anything with it to fix it.

So I had no choice but to reinstall Windows from scratch and reinstall and restore all my software and files. Took about 7 hours.

Not happy!

An issue with the USB Type-C in Windows 10 version 1809.

If a user connects a USB Type-C device ( including chargers ) during the shutdown or sleep process, it can cause a 60 second delay in the system sleep or shutdown process.

Normal functioning of the device is not affected. Its updated to 1903.

Yesterday evening I updated Windows 10 on my PC to 1909. Everything was fine, just a quick update.

Today I saw that all my VMs in VMWare Workstation don't work anymore. And they contained all my work for university.
Okay, let's just revert back to 1903. This can't a problem, right?

But Windows decided that it should revert back to 1809, not to 1903.
Also that was my home PC, and I had remote connection.
Yes, now it doesn't work too, because Windows removed Chrome Remote Desktop while reverting.

Thank you, Windows.
Thank you, Workstation.

Just updated to ( lol was forced to update to, because Microsoft doesn't give a fuck about your internet plans ) windows 10 build 1809 ( shitbox ) which erased my documents folder, uninstalled some of my games ( The only reason I was still using windows) and uninstalled my graphics driver. What did those guys smoke while writing the code for this update???!!!!! I mean if this is a work of some notorious guy who is just trying to create chaos then kudos, but this update didn't leave a choice to permanently switch to linux.

So as a personal project for work I decided to start data logging facility variables, it's something that we might need to pickup at some point in the future so decided to take the initiative since I'm the new guy.
I setup some basic current loop sensors are things like gas line pressures for bulk nitrogen and compressed air but decided to go with a more advanced system for logging the temperature and humidity in the labs. These sensors come with 'software' it's a web site you host internally. Cool so I just need to build a simple web server to run these PoE sensors. No big deal right, it's just an IIS service. Months after ordering Server 2019 though SSC I get 4 activation codes 2 MAK and 2 KMS. I won the lottery now i just have to download the server 2019 retail ISO and... Won't take the keys. Back to purchasing, "oh I can download that for you, what key is yours". Um... I dunno you sent me 4 Can I just get the link, "well you have to have a login". Ok what building are you in I'll drive over with a USB key (hoping there on the same campus), "the download keeps stopping, I'll contact the IT service in your building". a week later I get an install ISO and still no one knows that key is mine. Local IT service suggests it's probably a MAK key since I originally got a quote for a retail copy and we don't run a KMS server on the network I'm using for testing. We'll doesn't windows reject all 4 keys then proceed to register with a non-existent KMS server on the network I'm using for testing. Great so now this server that is supposed to connected to a private network for the sensors and use the second NIC for an internet connection has to be connected to the old network that I'm using for testing because that's where the KMS server seems to be. Ok no big deal the old network has internet except the powers that be want to migrate everything to the new more secure network but I still need to be connected to the KMS server because they sent me the wrong key. So I'm up to three network cards and some of my basic sensors are running on yet another network and I want to migrate the management software to this hardware to have all my data logging in one system. I had to label the Ethernet ports so I could hand over the hardware for certification and security scans.

So at this point I have my system running with a couple sensors setup with static IP's because I haven't had time to setup the DNS for the private network the sensors run on. Local IT goes to install McAfee and can't because it isn't compatible with anything after 1809 or later, I get a message back that " we only support up to 1709" I point out that it's server 2019, "Oh yeah, let me ask about that" a bunch of back and forth ensues and finally Local IT get's a version of McAfee that will install, runs security scan again i get a message back. " There are two high risk issues on your server", my blood pressure is getting high as well. The risks there looking at McAfee versions are out of date and windows Defender is disabled (because of McAfee).

There's a low risk issue as well, something relating to the DNS service I didn't fully setup. I tell local IT just disable it for now, then think we'll heck I'll remote in and do it. Nope can't remote into my server, oh they renamed it well that's lot going to stay that way but whatever oh here's the IP they assigned it, nope cant remote in no privileges. Ok so I run up three flights of stairs to local IT before they leave for the day log into my server yup RDP is enabled, odd but whatever let's delete the DNS role for now, nope you don't have admin privileges. Now I'm really getting displeased, I can;t have admin privileges on the network you want me to use to support the service on a system you can't support and I'm supposed to believe you can migrate the life safety systems you want us to move. I'm using my system to prove that the 2FA system works, at this rate I'm going to have 2FA access to a completely worthless broken system in a few years. good thing I rebuilt the whole server in a VM I'm planning to deploy before I get the official one back. I'm skipping a lot of the ridiculous back and forth conversations because the more I think about it the more irritated I get.