Windows 10 Fall Creators Update - Here is everything you need to know - Out Now!

[GoodBytes]

I cannot confirm if SMBv1 will only be disabled by default on a clean install or disable at upgrade, or be completely removed. My system has been upgraded to the "Skip Ahead" Insider programs, making me be in this hybrid Fall Creator Update and Redstone 4 release until the next release which will probably be late next week. My work PC has newer versions of many apps than my device.

[GoodBytes]

2 minutes ago, Sniperfox47 said:

@GoodBytes ReFS can still be used, just not created, from Pro right? My whole setup isn't going to crash and burn until I get Pro for Workstation, is it?

Correct. While I diodn't test this, if I am not mistaken, based on my understanding, you can still use ReFS formatted drives, just can't format it.

[TidaLWaveZ]

3 hours ago, SlipperyPete said:

and? this is a thread discussing new features tweaks to a Windows update. Mac OS has had many features before windows but this isnt the thread where we are discussing that.

Lol, you expected something else from someone who literally has an Apple themed username and an apple themed picture?

[Juniho]

gpu usage stats been on mine for months,i think i'm in the insider program though

[GoodBytes]

4 minutes ago, Juniho said:

gpu usage stats been on mine for months,i think i'm in the insider program though

Yes you are.

[MyName13]

Why wasn't GPU usage a thing since the beginning of times? 

[Kamina]

Seems pretty neat.

[nicolas2465]

Might want to fix your grammar.

[GoodBytes]

1 minute ago, nicolas2465 said:

Might want to fix your grammar.

Care to help?

[GoodBytes]

12 minutes ago, MyName13 said:

Why wasn't GPU usage a thing since the beginning of times? 

Well... standard needs to be put in place... and really, actual GPU on most systems, and not just gaming PCs started back in 2006 with Vista... before Intel integrated graphics and other solution that most PC used like VIA and S3 where not actual GPUs. They were like onboard sound chips... where it needs the CPU to do all the work, and it just takes the data convert it to whatever video connector and output (pretty much). They did include some hardware acceleration for video and DVD playback, and a few effects like basic shadows for Windows support, but that is pretty much it.

 

If you recall, beside the OS bugs, on most system Vista could not move many or any window smoothly, because not only the shell was actually GPU rendered instead of CPU, but you had transparency (glass effect), a taxing process for non-high-end GPU of the time. This is where VIA and S3 graphics pulled out of making graphic chips, and Intel pull themselves together and make a graphic chip to handle all this, forming an actual GPU... and things got fast enough by the time Windows 7 come out, 3 years later.

[SlipperyPete]

1 hour ago, TidaLWaveZ said:

Lol, you expected something else from someone who literally has an Apple themed username and an apple themed picture?

i actually really like @DrMacintosh i think they provide a lot to the forum and see them a lot on threads that dont pertain to mac stuff. its was more of a friendly nudge to stay a bit more on topic.

[SlytherJack]

Does anybody care about font smoothing like the OSX does? When will you start taking it seriously MS? Font looks terrible on my already pathetic laptop display.

[GoodBytes]

Just now, SlytherJack said:

Does anybody care about font smoothing like the OSX does? When will you start taking it seriously MS? Font looks terrible on my already pathetic laptop display.

That is your display. Sorry

What laptop do you have? (or what is the screen resolution and size)?

[DrMacintosh]

23 minutes ago, GoodBytes said:

That is your display. Sorry

He is right though, MS could work on smoothing out the UI and text. 

[GoodBytes]

4 minutes ago, DrMacintosh said:

He is right though, MS could work on smoothing out the UI and text. 

Sorry no. Microsoft can't fix low resolution displays and TN/*VA panel limitations, the same way that they can't magically add performance out of a computer.

Crappy hardware is crappy hardware.

 

Apple displays are high-DPI, featuring decent IPS panels. The OS is high-DPI aware like Windows (although some less used panels in Windows aren't, but that is not the conversation), and so text looks smooth, easy to read like a decent and premium grade smartphone display.

[outercry]

Funny that my W10 is still running even without the Creators Update, because something went wrong with it, and it doesn't even prompt me about it. I know you could do the update manually, but I heard that some people had big problems after doing that, so I didn't bother.

 

I still have this text greet me, when I open my Windows Update page: Good news! The Windows 10 Creators Update is on its way. Want to be one of the first to get it?

 

Anyhoo, hoping this new update resolves the problem with the previous one.

[Donut417]

6 hours ago, ZackBarletto said:

If it is the original windows 10, I thought they were ending support for that. Hurry my friend!

https://linustechtips.com/main/topic/844769-microsoft-officially-discontinues-support-for-windows-10-november-2015-update/

 

Do get any UI issues or search issues? That's the only issues I face when I need to update to the "creators" on various computers.

 

Sweet, thanks!

Im running version 1607. It says the update is available but they haven't pushed it down to the machine yet. I didnt update manually because when the update came out it fucked up a lot of machines. 

 

I do have UI issues. My mouse cursor gets distorted. It eventually fixes itself. Before some one says a borked install, its happened on this machines for the last 3 installs. 

[Trixanity]

1 hour ago, GoodBytes said:

Sorry no. Microsoft can't fix low resolution displays and TN/*VA panel limitations, the same way that they can't magically add performance out of a computer.

Crappy hardware is crappy hardware.

 

Apple displays are high-DPI, featuring decent IPS panels. The OS is high-DPI aware like Windows (although some less used panels in Windows aren't, but that is not the conversation), and so text looks smooth, easy to read like a decent and premium grade smartphone display.

To be fair, the MacBook Air does have a 1440 x 900 TN panel.

 

I'm not aware of any issues on Windows though. I also thought Windows had some font smoothing.

 

In any case, I'm guessing it comes down to the same problem high DPI displays have on Windows: developers don't support it and the API only works with UWP.

[LAwLz]

11 hours ago, GoodBytes said:

Sorry no. Microsoft can't fix low resolution displays and TN/*VA panel limitations, the same way that they can't magically add performance out of a computer.

Crappy hardware is crappy hardware.

 

Apple displays are high-DPI, featuring decent IPS panels. The OS is high-DPI aware like Windows (although some less used panels in Windows aren't, but that is not the conversation), and so text looks smooth, easy to read like a decent and premium grade smartphone display.

Buying a high resolution display would make text look nicer, but what I think he is talking about are font rasterization engines.

 

For those who don't know, that's the engine responsible for converting the vectors to bitmaps which are mapped to the pixels on your screen and some include subpixel rendering to make things smoother.

Windows uses ClearType, while MacOS and many other operating systems use FreeType.

(If we are going to be picky, the font rasterization engines in Windows are DirectWrite, GDI and Uniscribe, and ClearType is the name for the subpixel rendering used in them)

 

ClearType is more strict with adhering to pixel-grids because at very low resolutions that makes letters sharper and thus clearer to read.

FreeType tries to preserve the aesthetics of the font even at lower resolutions, at the cost of slight blurriness.

 

Here is a comparison I just made (please note that it will not look the same for you as it does for me unless you have an RGB subpixel layout).

 

Quote

 

 

 

And here is a comparison zoomed in 400% to make the difference slightly more obvious.

Quote

 

 

 

 

Please note that this is not meant to be some scientific test comparing FreeType vs ClearType. I just want to show that fonts will look different on different systems. And which rendering is the best is very subjective, people will mostly prefer whichever one is the most familiar to them.

 

Also, the FreeType image is from Ubuntu, which is slightly different from how MacOS would render it.

[GoodBytes]

1 hour ago, Trixanity said:

To be fair, the MacBook Air does have a 1440 x 900 TN panel.

Yes.. beside that one... and the text is just as bad as a typical laptop on the PC side.. Yes i saw the system in action. Beside the CPU (and associated chipset) being updated, and even then 5th gen Core i5/7 CPU, Apple never actually updated the system. Very sad.

 

Quote

In any case, I'm guessing it comes down to the same problem high DPI displays have on Windows: developers don't support it and the API only works with UWP.

That is not true. The APIs works on Win32. The problem comes down to programs using custom GUI frameworks, where were never designed for any DPI level beside the default one. So implementing this is very resource consuming (time and money). And this is not helped by the fact that "Now It's High DPI aware!!!" isn't a particular selling feature. So it is not pushed. So in a way, their custom GUI framework that they worked on, has an architectural flaw and it is very costly to fix.

 

But you have a nice collection of high-DPI aware programs now, and it is growing. Beside Windows built-in programs, you have: Firefox, Chrome, Microsoft software (Skype Win32, Visual Studio, Visual Studio Code, Blend, Office), Logitech latest mouse driver panel, Nvidia Control Panel, AMD Control Panel, FileZilla FTP, SmartFTP, AIDA64, MobaXtern, Paint.NET, Photoshop, and many others.

[LAwLz]

28 minutes ago, GoodBytes said:

That is not true. The APIs works on Win32. The problem comes down to programs using custom GUI frameworks, where were never designed for any DPI level beside the default one. So implementing this is very resource consuming (time and money). And this is not helped by the fact that "Now It's High DPI aware!!!" isn't a particular selling feature. So it is not pushed. So in a way, their custom GUI framework that they worked on, has an architectural flaw and it is very costly to fix.

 

But you have a nice collection of high-DPI aware programs now, and it is growing. Beside Windows built-in programs, you have: Firefox, Chrome, Microsoft software (Skype Win32, Visual Studio, Visual Studio Code, Blend, Office), Logitech latest mouse driver panel, Nvidia Control Panel, AMD Control Panel, FileZilla FTP, SmartFTP, AIDA64, MobaXtern, Paint.NET, Photoshop, and many others.

You can not push all the blame to third party developers using custom GUI frameworks. Not even Microsoft has coded their programs for high DPI awareness properly.

Internet Explorer, Notepad and a bunch of other programs got proper support in the creators update for Windows 10. Before then they might have been partially high-DPI aware, but they couldn't do things such as scale accordingly if you moved the window from a high-DPI monitor to a low-DPI monitor.

 

Also, this is a direct quote from Peter Felts who works with high-DPI scaling in Windows, and this was posted in April this year (so fairly recently):

Quote

As of writing this blog, the high-DPI documentation available on MSDN is horribly outdated. The guides for writing per-monitor DPI aware applications were written in the Windows 8.1 timeframe and haven’t seen any significant updates since then. Also, many Windows API have DPI sensitivities that are not documented. That is to say that some Windows API will behave differently if they’re being called from a system-DPI-aware context vs. a per-monitor DPI aware context.

 

Here is a post about making Notepad per-monitor DPI aware. As you can see, it is fairly complicated (this is just for making it per-monitor-DPI-aware, since it was already system-DPI-aware). If Microsoft themselves had so many issues using their own APIs to turn a simple program like Notepad properly DPI aware then you really expect developers to put in the time and effort to do it either.

Hell, Microsoft even said:

Quote

We recognize that these, and many other, platform features are going to be needed by developers before they’re fully unblocked from updating their desktop applications to handle display scaling well.

 

Microsoft's APIs have been lackluster, and the documentation has too.

[TheCherryKing]

Is it possible to copy the task manager from this Windows 10 build to Windows 8.x?

[Exotath]

Adding the GPU to resource monitoring is awesome!

[Doobeedoo]

Nice for GPU details in task manager. Still no universal settings which expected. Also the Fluent Design not fully done as well as File Explorer still got no update which is very much needed. Needs dark theme option and tabs for start.

[Notional]

Great with performance diagrams for GPU now. Love it.

 

But what about HDR? When will W10 actually support HDR properly?