Discussion in 'other software & services' started by stapp, Aug 3, 2016.
With any Windows OS , Clean install is the golden rule.
So it doesn't detect if a newer driver is installed? That's bad for both Microsoft and AMD, the driver should detect a newer one. It does when you're doing it yourself, and it should do with the drivers provided by AMD to Microsoft.
So now my dilemma is do I stick with 1607 and just hope some future Windows update sorts out my hanging shutdown / restart problem, or go back to 1511 and periodically retest with 1607 image after new updates to see if it is sorted? The issue is I have a lot of software I like to keep updated, but I think it would be too much PT to do this in both versions.
Microsoft should produce two lines of Windows going forward:
A stable version like Enterprise LTS and the rolling version like Windows Home/Pro.
And it should let consumers decide if they want stability or get the latest Windows on the bleeding edge.
OpenSUSE does that with its Leap and Tumbleweed versions.
They probably think they are already doing this by having a release version and the insider builds. Some might agree. Others will not.
I had a similar problem: my original graphic card was AMD Radeon HD 8870M in Windows 8. After the upgrade to Win 8.1 it became AMD Radeon R9 M200X Series which was good for the Win 10 upgrade.
After doing the AU, my display brightness could not be adjusted anymore and it would remain very dimmed most of the time. I tried to update the AMD driver through Radeon but didn't work, then I tried through Device Manager/Display Adapters, and it updated through Windows to AMD Radeon HD 8600/8700, a real disaster. I had to restore an image back to Win 10 V. 1511 (no AU) which works marvelously. Luckily MS is not yet pushing AU through Windows Update, so I prefer to wait until they settle this issue.
Downloaded and installed 1607 on my real hardware.
It runs fine, is way more polished than 1511, and I didn't have driver issues.
The Start Menu changed and the layout is worse than before.
There are more update settings and privacy settings to tweak, most of which still are disabled by Destroy Windows 10 Spying or ShutUp10 or Spybot Anti Beacon.
The Settings panel (Metro style) works better now, it has a good search function, the "Back" button actually goes back to where you were even if the previous page was not in the same category.
I can see performance improvements as well.
The system installed and activated fine. All drivers work, and the AMD driver is version 16.3.
Right after installing it, I noticed that the "Get Going Fast" button now is right aside another button of the same size that says "Customize", which is great. However, upon creating a new account, the "Skip This Step" option, used to create a LOCAL account and not use a Microsoft account, is still small and could escape the eye.
Some Group Policy options don't anymore, like the "Do not display the Lock Screen".
"Configure Automatic Updates" is working as far as I can tell.
Disabling "Automatic App Update" via Task Scheduler made the widgets to not download on a new account, showing only "A new app is coming" or similar. I had to create a new account, log into it, copy it's "TileDataLayer" folder to my folder (C:\Users\Amarildo\AppData\Local), edit the permissions of this folder, and then do "sfc /scannow" to be able to use the Start Menu.
Other than that, I'm not seeing any major issues.
Windows 10 AU doesn't like HP 2000 Notebook PC. One of the associated drivers for Realtek PCIE CardReader is blocked in the name of system stability. There is a driver update you can manually download that'll work.
A more serious issue that makes the system very sluggish to unresponsive for several minutes. I've investigated this, and is a problem with Realtek RTL8188CE 802.11bgn WiFi Adapter - Driver version: 2016-03-31, and being connected.
Currently no available driver that I'm aware of exists. The previous Windows 10 build, had used a driver that wasn't digitally signed. Recovering the drivers and trying to use makes Windows 10 complain about not digitally signed.
Options; Don't use WiFi, and pray a driver becomes available that addresses system stability. Or replace WiFi card, or rollback to previous Windows 10 build. Or install back the Windows 7.
Replace Realtek wifi card with a Broadcom wifi card. Realtek sucks on Linux.
most drivers suck on Linux , they just gives the minimum required; i had to use an Nvidia driver which can't allow me to use my TV as secondary display while on Windows it can...
Linux is for geeks or at least user with decent computing skills, whatever Linux fans may say.
Installed clean install. Everything good, except my nVidia card. I run an older one, the GTS 240. Installed is 341.74. Every time I update to the latest driver, 341.95, after rebooting it always re-installs the older driver! Every time! Anyone else having this problem?!
That's not a problem, it's a feature. Windows 10 knows better than you, obviously.
Joking aside, right click the start icon>System>Advanced system settings>Hardware tab>Device installation settings>select "No" and save changes.
Then, go to Device manager, double click your nVidia driver>roll back driver. Go through the procedure, and I think there's a "revert permanently" checkbox but I might be wrong.It should permanently revert to the desired version.
Stop Windows 10 Anniversary Update from installing Candy Crush and other unwanted apps
Thanks! Worked for now. But I guess that's a system-wide setting? Now other devices won't auto-update?
It's system wide. You could try setting "Yes" in Device installation settings and see if the rolled back driver will stick. I haven't tried it as I want manual control of all drivers.
That won't work for those with Home editions.
True, indeed. However, the winaero dev is currently looking into a resolution for home edition users. If you look further down in the comments on that page, he has suggested some registry key modifications for home edition users. But I would suggest that home edition users wait until that has been thoroughly tested and confirmed.
Link a Microsoft Account to a Windows 10 license
Resolved! Today I have received the update of Photos (v16.722.10060.0) via Windows Update and the application began to work. Thanks @Phant0m and others for valuable comments and help provided. It looks, though, that MS have been aware of issues with Photos and they did their homework to fix it. I wonder if MS telemetry contributed to resolve it. Anyway my faith in Microsoft capabilities to resolve also the reboot/shutdown issue grows.
The only thing that worries me is that it doesn't seem to be a common problem.
At the moment I am running AU on my older secondary laptop without issues, but 1511 on my primary one, with 1607 upgrade hidden via wushowhide, and with an AU image I intend to occasionally switch to, to keep it current, and in the hope they detect and fix what is probably a driver issue.
Yeah, it could be but remember that only more knowledgeable users go to forums, supports, helpdesks etc. if they encounter an issue. The majority of Win users (i.e. ordinary users) will rather power shutdown a machine and will wait for a fix. But MS telemetry will catch this anomaly. So my conclusion is (reinforced by today's fix for Photos application) that even if an issue isn't widely (publicly) discussed it doesn't necessarily mean that Microsoft is not aware of this problem and they can silently work on it.
MS works on a fix. Discussion here
Sounds like that the so much critisized win10 call home capability works also to the benefit of end users.
Wish it would be the only and prime aim but frankly despite of its controversy I still think that the telemetry is the great helper in identifying problems. We need to consider that majority of users don't report problems. Unfortunately collected information can be also misused but it's another story.
Separate names with a comma.