freitasm:

mattwnz:

I noticed that after the update, it changes the 'choose how updates are delivered' settings. It sets it so future windows updates are set to now download over other peoples PCs again . I know I had previously disabled this on my PCs, but they re-enabled it. Ironically I had to reenter my password to disable it disabled it again, yet Microsoft re-enabled the setting to enable it without my permission with the update. You really have to watch this sort of thing.

Just checked this and you're correct.

Microsoft should not change previous settings that don't directly impact the system operation.

gzt:

freitasm:

 

mattwnz:

 

 

 

I noticed that after the update, it changes the 'choose how updates are delivered' settings. It sets it so future windows updates are set to now download over other peoples PCs again . I know I had previously disabled this on my PCs, but they re-enabled it. Ironically I had to reenter my password to disable it disabled it again, yet Microsoft re-enabled the setting to enable it without my permission with the update. You really have to watch this sort of thing.

 

 

 

 

 

 

Just checked this and you're correct.

 

 

 

Microsoft should not change previous settings that don't directly impact the system operation.

 

It will be interesting to see how Microsoft deals with these reports.

Ideally they will re-release Anniversary to address these and other issues before it goes to CBB.

but maybe the answer will be: If you don't like it then don't install it. Standalone CBB cannot defer forever so that answer would imply going one step further into a managed environment to avoid it.

Pending: link to ms branch info.

This is the sort of behaviour that leads to companies losing the trust they have built up. I am not sure, but I'd be surprised if this doesn't contravene EU standards for business practices. 

Pretty sure MS has fallen foul of them in the past as well. 

I got to thinking today (first time in a while) -- I wonder if MS is having a mismatch between the statistical sample of machines that are insider machines, and the rest of the non-insider machines out there.  If others are anything like me, I have an insider install on an old machine, out of interest, but not on my main machine (which is running original Win 10).  From what I read, it seems like MS is currently having trouble with machines with SSD drives, or partly with SSD machines, which will be poorly represented among older machines, but over-represented in newer machines.  Additionally, again from what I read, they are updating newer machines to Anniversary before older machines, so are finding this problem sooner.

Since my main machine is running a hybrid main drive, I'm thinking I might not want to update any time soon!

Looks like my wifi failure is just bad timing. Other than that no dramas at all with any machines and the update other than it REBOOTING MY COMPUTER WHEN I HAD THINGS OPEN. which is why I disable the update service after I have used it on the gaming PC and the other ones I do actual stuff on.

richms:

 

Looks like my wifi failure is just bad timing. Other than that no dramas at all with any machines and the update other than it REBOOTING MY COMPUTER WHEN I HAD THINGS OPEN. which is why I disable the update service after I have used it on the gaming PC and the other ones I do actual stuff on.

 

Yeah I've had that too. Don't know if it is still an issue with Anniversary since I keep the service disabled except when I feel like updating. 

They have added the ability to set the hours you use the computer so it will not restart during those, but only allow for a maximum of 12 of them in a day.

freitasm:

 

I am currently using EDGE but I wonder if the problem with Tweetdeck is something related to its Javascript engine or add-ons (LastPass installed).

 

What worries me is that at some point they have to release a full OS update to update the browser (although I know it was said before that EDGE is an app and can be updated separately, etc).

 

You may find that the Edge browser is on a similar release cycle to windows, hence the long time between updates.  The Javascript engine is Chakra (similar to that on IE11).

One of the things that I like about IE is that it has a relatively modular COM based architecture. You can easily drop a web browser control into a windows forms application in Visual Studio without much effort of development.

MASSIVE keyboard lag since the anniversary update. Lucky it's on a machine I don't use much.

When I do use it, I can't even type a password into a browser without waiting 5 seconds between characters. 

Not happy in the slightest. Will be rolling back this weekend.

TwoSeven: You may find that the Edge browser is on a similar release cycle to windows, hence the long time between updates.  The Javascript engine is Chakra (similar to that on IE11).

 

Yes, it's on a similar release cycle but earlier talks were about Edge being an app itself so it could be independent of the OS. 

I've had repeats of 2 minor problems I had initially with Windows 10 when I upgraded in Feb/March this year. The issues were fixed a few months later. On the laptop, after disconnecting the wifi and hibernating/restarting I am able to connect to the wifi network, but unable to get an internet connection. Repeated attempts fail but a reboot and then retry works ok.

On a desktop, after restarting from hibernation, the lock screen appears, hit enter and then most of the time there is no response to enter, but mouse click works. In the anniversary edition only, there is sometimes a blue background instead of a proper picture.