Windows 10 October 2018 Update rollout now paused
-
Something is not quite right between OEM's and MS.. there was a time when Win10 WU drivers could be trusted but lately it seems they are all over the place. ... neither party are testing or communicating properly.
There is a lot fundamentally wrong at what's going on with MS management, IMHO.
-
-
Something is not quite right between OEM's and MS.. there was a time when Win10 WU drivers could be trusted but lately it seems they are all over the place. ... neither party are testing or communicating properly.
There is a lot fundamentally wrong at what's going on with MS management, IMHO.
I'll say!
Check out this.
LAN drivers for the ASUS ROG Maximus X Hero, notice the dates and drivers highlighted.
click to enlarge:
-
Hi Superfly !
Edwin said ; " You can get it to work for Taskbar by way of dll injection, Disable Dark Taskbar Menu, but you need to run the .bat every time Explorer starts or restarts. "
Can you make a scheduled task ( has to start with every reboot ) of this .bat ...........??
Lots of people ( and me) want it in 1809 , coz its only grey and dark , we want more white and light-blue , we all want 1809 more "good looking " ......!!
-
I'll say!
Check out this.
LAN drivers for the ASUS ROG Maximus X Hero, notice the dates and drivers highlighted.
click to enlarge:
Hmmm... thanx bud 
Hi Superfly !
Edwin said ; " You can get it to work for Taskbar by way of dll injection,
Disable Dark Taskbar Menu, but you need to run the .bat every time Explorer starts or restarts. "
Can you make a scheduled task ( has to start with every reboot ) of this .bat ...........??
Lots of people ( and me) want it in 1809 , coz its only grey and dark , we want more white and light-blue , we all want 1809 more "good looking " ......!!
I'm looking at the source code of the dll (I found it at github) to see if it can be adapted for the explorer menu as well ... I want to go through that first to get a grip of things...
-
-
" I'm looking at the source code of the dll (I found it at github) to see if it can be adapted for the explorer menu as well ... I want to go through that first to get a grip of things... ".............would be really awsome !!
Its only for taskbar , but if it can be adapted for the explorer menu as well .............would be double awsome !!
( I know lots of people , incl. me , would be very happy with the good looking 1809 !)
-
![]()
Bit more evidence for what is being deleted.
I did actually lose two files during the upgrade. I have the desktop synced to OneDrive, not the Documents, nor any other of the standard locations (Documents, Downloads, Pictures, Videos, etc.)
One Drive has it's own contents there (usually screenshots if Dropbox doesn't offer to save them, I don't really care where they go as once they're edited and uploaded they are normally redundant). I do sync stuff to Dropbox (again not mission critical) for collaborative purposes (or Google Drive if that's the other collaborator's poison).
For some reason, because I have the files pinned in Libre Office, I didn't see the need to move them as the desktop is cluttered enough (but it's my workspace and I kind of like the idea that it would roam with me if I logged into A.N. Other device).
None of the file storage locations are changed. OneDrive being set to 'cloud' the desktop meant it deleted the contents of C:\Users\%username%\Desktop
C:\Users\%username%\OneDrive\Desktop was fine as was C:\Users\%username%\Documents et al.
So I did have a backup in the File History dated 28th September (last edit) but nothing after 2nd October (when I did the upgrade). Save locations are default in the storage location options.
-
Something is not quite right between OEM's and MS.. there was a time when Win10 WU drivers could be trusted but lately it seems they are all over the place. ... neither party are testing or communicating properly.
There is a lot fundamentally wrong at what's going on with MS management, IMHO.
Hehhe, first MS screw up the driver compatibility and the OEM get notified by MS. Then OEM starts to fix the issue, while MS releses a patch. When finally the OEM fix comes out, we again have an issue and the whole process start all over... or something in that direction.
On a few builds I have literally tested over 200 different Intel/nVidia driver combinations, and they all refused to work together. While the same (every single one) drivers work flawlessly on another Windows build. Yet MS blame the OEM for bad drivers and refuse to accept that the issue is/was in the OS.
-
Hehhe, first MS screw up the driver compatibility and the OEM get notified by MS. Then OEM starts to fix the issue, while MS releses a patch. When finally the OEM fix comes out, we again have an issue and the whole process start all over... or something in that direction.
On a few builds I have literally tested over 200 different Intel/nVidia driver combinations, and they all refused to work together. While the same (every single one) drivers work flawlessly on another Windows build. Yet MS blame the OEM for bad drivers and refuse to accept that the issue is/was in the OS.
Gotta say T, I'm totally in your corner
-
My PC is a self build and the hardware is getting old. The newest component is a Nvidia 980GTX. The chipset is Ivybridge era. Of the many complaints i have with Windows 10, Driver issues aren't one of them. I haven't had a single problem, except having to reinstall my Soundcard Drivers after the twice yearly feature updates. I haven't had a single BSOD or other major crash either since day1.
Thought it might be nice to share something positive for a change. WU still sucks though. 
-
-
My PC is a self build and the hardware is getting old. The newest component is a Nvidia 980GTX. The chipset is Ivybridge era. Of the many complaints i have with Windows 10, Driver issues aren't one of them. I haven't had a single problem, except having to reinstall my Soundcard Drivers after the twice yearly feature updates. I haven't had a single BSOD or other major crash either since day1.
I don't tend to have problems either. One reason is likely because I never use a Microsoft supplied driver unless nothing that works is available for download from the manufacturer. I don't even trust MS to pass on the manufacturer's driver since I'm not convinced they haven't tampered with it.
