I have a violet reaction to that image.
Killing the Cortana process fixed it. Hopefully installing 1809 won’t break it again.
Is pink mandatory now?
lol - no, just one of many themes
Interesting. Guess some of us will be skipping 1809 altogether.
Someone still running Windows 10 1803 in, say July, will be able to skip 1809 entirely by calling up “Download and install,” which will then deploy the latest version, Windows 10 1903.
RichVR
4078
I was in New Dawn, in Jumpgate. And that is a travesty. Pink is the color of Flux!
Soma
4079
put hand up
I moved from 1803 to 1809 after they deemed it “business ready” i.e. “we use Win 10 Home users as beta testers and the beta testers say it is now good enough”.
It is ok so far, some mystery reboot aside.
I’m not gonna jump into 1903 until 3-6 months after official release, i.e. when MS deem it “business ready” again.
fdsaion
4080
0/4 now - 1809 continues the traditional on the old XPS 13 with a reboot loop. Took a full reinstall.
And to add to that, it also blew up the wifi on a new laptop (Huawei Matebook X Pro) - either errors out on connect attempt, or “connects” w/o data being sent. This one got reverted to 1803 for now since I’m traveling and unable to deal with a full reinstall or driver fuckery.
Yeah still not going to move the desktop to Win 10.
I tested out 1809 in my virtual environment, powered by VMWare VDI, and the boot up times exploded from 1 or 2 minutes to almost 20 (!!!) and it when the damned system would finally provision itself, it seemed to have some performance issues as well. Some of that is VMWare needing to update their tools, of course, but I’m not looking forward to keeping my Windows 10 virtual environment updated from what I’ve experience twice now, so far.
“Oh, we don’t support that in 1803” I heard like 3 times on the phone with various software vendors in the last six months. Super duper.
So you guys, I leave my PC on 24/7. I’ve noticed I need to reboot Win10 every few days or it gets unstable. Stuff won’t load and I get some sort of “windows can’t be created” error when I load something.
Is this normal for Win10? I could leave Win7 up for ages and not have this issue.
Thanks y’all.
It is very rare for me to reboot W10 on my desktop. It is quite stable. I reboot chrome more often than windows I think (for updates).
When you get back to your PC, what is its status? Did it autolock, and you have to log back in again? It sounds as if you don’t ever lock it and it’s perpetually awake or something.
Yeah. If you’re running a “clean,” bare Windows 10, have no hardware issues, and you’re not locking or running auto-updates, it should run perfectly fine in perpetuity. Any additional software, services, etc. is likely where you’re getting bogged down.
There’s a practice in a client with large number of windows servers that requires every machine to reboot during off-peak hours. It’s no joke.
Yeah, it’s always awake. Usually I notice a problem when DisplayFusion has crashed. Ugh.
I hate to say “memory leak” but that window error sounds like some sort of resource is unavailable because something running is gobbling everything up. Kinda like the handles of the olden days. I don’t know thought.
Gah, I bet it’s Opera. Fucking browsers.
It’s probably some obscure little program you always have running and never notice… A tiny one like a printer monitor … or that soundswitch thing … whatever it is you’ll never find out!
edit: Idea, create a new account on same windows and use it for a while to see if error exists again.
Hah, time to start experimenting. Thanks guys!
Task Manager should be able to tell you if you’re about to run out of memory, or if the CPU is 100%, or if there’s a lot of disk activity, and which processes are the top offenders. If not, then the programs “Process Explorer” or “Process Hacker” should be able to do so.
