I totally agree with you RocknRobert, not only the motherboard firmware but also all of the drivers that are part of the system.
Windows File Explorer Not Showing Correct Folder Size If Folder Named 'Applications'
Since installing the 1803 update, Windows File Explorer doesn't display the correct folder size if the folder is named 'Applications'.
There seems to be a bug that if the folder name is 6 characters or more and starts with 'Appli', the folder size shows significantly less than it actually is. For example if the folder is named 'Apps' or 'Appli', it will display the size correctly. If however it is named 'Applications' or 'Applix' or 'Appliy', then it won't display correctly.
The Feedback app doesn't work on my computer due to having telemetry settings set to 'Basic', therefore I am reporting the bug here instead.
OS Version:
Windows 10 Pro X64 (17134.1, 1803)
Screenshots:
Windows for home | Windows 10 | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
102 answers
Sort by: Most helpful
-
Anonymous
2019-03-16T03:57:33+00:00 -
Anonymous
2019-03-16T02:20:30+00:00 I'm just saying if you ignore your motherboard firmware upgrades you are looking for trouble, because the last time I upgraded that's what bailed me out...!
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2019-03-15T22:42:05+00:00 So one whole year has passed and this **** company didn't fix it?
-
Anonymous
2019-03-15T20:21:06+00:00 I have 4 different computers, I am currently running 1809 on my desktop and 2 laptops and running Windows 10 Version 1703 on another laptop. the laptop running 1703 work as it should. The three that are running 1809 all fail in exactly the same way. I would say that it is a bug that Microsoft introduced/reintroduced when 1803 was released and not a hardware/firmware problem. If I restore my desktop to a version before 1803 it works as it should.
I find it a bit insulting that Microsoft is totally ignoring all of these comments!