New
#60
Will wait .............if I only know whats breaking Win-startmenu , in 2004 .
In 1909 works perfectly , together with Open Shell .........in 2004 only Open Shell is ok !
CS still works fine for me.
Here's what I've noticed in this build 2004:
- Heavy games in full screen (in my case, I play AC Odyssey, Control, Far Cry 5, among others), if you use "ALT + TAB" to return to the Desktop, after executing this action for a few times, the game will at a certain moment, disappear from the screen and memory! Crash!
- MSWinodws Explorer chokes when reading many files. My drive is a 120GB SSD for the operating system only.
- Sometimes I notice that the system pauses and comes back ...
- None of these symptoms were seen in build 1909!
- I'll have to go back to the previous build ... again, format and reinstall the system ...
- thanks MS!
much like the 1903 update, the desktop took awhile to download/install 2004. This time with some added 'fun' before things got rolling.
Started the download at 1pm. The wifi connection randomly dropped multiple times about an hour in but it got to an install. A little after 3pm, the first install failed with a 0x8024200d error ("Needs Another Download") when it was around 20% (similar percentage as the percentage of the drop during the download). It restarted automatically, downloaded in about an hour, and took 4 hours to get from 0 to 100 on the install. Followed by about 3 hours on the restart. Everybody else is gonna have to work hard to keep that 16 minute average on offline time.
If the 1903 pattern holds true, the laptop should take way way quicker to download/install the update (For 1903, it took like 8 hours to install on the desktop and 2 hours on the laptop). I'll install on the laptop in a few days or so. Lots of time until the 14th of July and it's not like sports is actually gonna happen (in the US) until then.
This one for printers....
[ADDED 6/12] After installing this update, certain printers might fail to print. The print spooler might throw an error or close unexpectedly when attempting to print, and no output will come from the affected printer.
You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app might close unexpectedly.
Note This issue might also affect software-based printers, for example printing to PDF.
...isn't affecting my 19041.329, not for the Microsoft Print to PDF anyway. Tested printing from Notepad and Firefox.
I also tab in and out of full screen game windows without incident.