Creators Edition

Jivesinger

spud17 wrote: »

I'd seen the reports of problems with Broadcom Bluetooth drivers, but not for Broadcom 440x 10/100 ethernet drivers.*
Microsoft advice is to not manually update, fair enough, but it was an auto update which did for me originally.:)

*edit: now found https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-creators-update-broke-my-lan-port/efad767b-b40a-469b-a815-9bff48dcd3c4

Mine is a Dell 6400, similar age/spec to some of those in the link below

https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/problems-with-creators-update/d5117f36-b66f-4590-b2f3-a64b92445385?rtAction=1492183836572

It was a Broadcom 440x which I was thinking of too.

I believe the best thread to watch for the Broadcom 440x issue is the second one you mentioned - someone from Microsoft confirmed on page 2 that it's a bug and they're hopefully working on a fix.

spud17

Jivesinger wrote: »

It was a Broadcom 440x which I was thinking of too.

I believe the best thread to watch for the Broadcom 440x issue is the second one you mentioned - someone from Microsoft confirmed on page 2 that it's a bug and they're hopefully working on a fix.

Last post regarding Broadcom 440x is 26th May and says they are working on it, i.e. 6 weeks have elapsed.
My issue arose about a week ago on the 20th May.
My desktop only updated the weekend before that.
Apparently the correct drivers are included in 1705, just that they do not work.
There is a workaround, disable NIC in the BIOS.

Jivesinger

spud17 wrote: »

Last post regarding Broadcom 440x is 26th May and says they are working on it, i.e. 6 weeks have elapsed.

I'd rather that they know about it and seem to be actively working on it, even if it's taken 6 weeks so far, than have nothing from Microsoft at all.

spud17 wrote: »

There is a workaround, disable NIC in the BIOS.

... if you are lucky enough to have such an option in your BIOS.

angryparcel

spud17 wrote: »

There is a workaround, disable NIC in the BIOS.

That is fine if you know what you are doing, but not everyone one this forum will be tech savvy like us to know what Bios is.

spud17

Jivesinger wrote: »

I'd rather that they know about it and seem to be actively working on it, even if it's taken 6 weeks so far, than have nothing from Microsoft at all.
... if you are lucky enough to have such an option in your BIOS.

I do have the option, but if I do disable it then the chances are the correct driver will not be offered via update, because it will not be detected? IYSWIM
Reading around, it may be that now Creators Edition will not be offered if it detects Broadcom 440x.
Laptop is saying no updates available, last updates were Cumulative Update KB4019472 and MSRT for May.

toshi

kwikbreaks wrote: »

I'd rather there were no feature updates at all if they are as banal as those mentioned in that article. Just fixing the vulnerabilities rather than creating more might even keep the update size down to reasonable levels and possibly even stop filling up my disk.

This is what I want. I hope security update (compulsory) and feature update (optional) would be clearly separated out. My use of Windows 7 update is very comfortable as maintenance (security) update only until 1.2020. I cannot survive if Windows update would kill my network connection, I hope windows 10 will be very stable by 2020....

A couple of days ago, I have found Windows 10 Creators Update Bloatware Free Edition lol. Does anyone try this? I was so curious how this lightweight Windows behave.

Edit: Warning:
(This is my test purpose only to understand memory usage, Don't try if you are not sure what you are doing.) also deleted the link - thanks to angryparcel : Edit End

http://www.****.com/ *****.html

I have just tested memory usage of my windows 7 and windows 10; I cloned my working Win7 environment to a spare SSD then perform windows10 upgrade. (Initially I cloned to hard disk and overnight windows 10 update failed !!! but Windows restored Windows 7 automatically ...)

Memory usage results: (This is the based upon my real environment.

My dirty Windows 7 (1.35-1.40GB) to Windows 10 Creators Update Bloatware Free Edition 5.3 (1.7GB)

Around 250MB to 300MB increased.

My dirty Windows 7 (1.35-1.40GB) to Official Windows 10 Creators Update (1.9-2.0GB)

More than 500MB increased.

I haven't played with a lot, but if you disable OneDrive, you can save 100MB. Less powerful, less memory (older) computers would suffer from "feature-rich" Windows 10 update. Please don't dump them!! (see the blow)

Another SSD recommendation for Windows 10 users lol (or LinuxMint? )
If your computer is struggling with windows 10, get an SSD. If you have only 2GB with Windows10, Get SSD (serious!) I have tested this with real working Windows10 environment, Windows aggressively transfers Physical memory to SSD swap file (virtual memory) once Windows Started (Give nearly 1GB free physical memory) But I don't see any significant slow down. If this happens to hard disk, Windows would freeze, as hard disk swaipfile is much slower than that of SSD. Point is that 2GB + SSD CAN SURVIVE WITH THE LATEST CREATOR WINDOWS 10 UPDATE

angryparcel

toshi wrote: »

A couple of days ago, I have found Windows 10 Creators Update Bloatware Free Edition lol. Does anyone try this? I was so curious how this lightweight Windows behave.

<link removed>

I

a clue is in where it comes from, it is not from Microsoft, these are scam sites that will place all sorts into the files (malware, adware, etc.)
and people wonder why they have issues.

toshi

angryparcel wrote: »

a clue is in where it comes from, it is not from Microsoft, these are scam sites that will place all sorts into the files (malware, adware, etc.)
and people wonder why they have issues.

Thanks for the comment, although I personally don't see any problems for my testing. but I added a warning massage. (Edit) I have just deleted the link. May be better to delete the link itself ? (Edit)

spud17

Update: Just checked and Microsoft look to have sorted a fix for the Broadcom issue.
At the moment it is being tested by some on the Windows Insiders, it's looking promising.
Bottom of page #11 onwards.
https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/problems-with-creators-update/d5117f36-b66f-4590-b2f3-a64b92445385?rtAction=1492183836572

Today we released a build that includes the fix for the Broadcom 440x. This fix was released to Windows Insiders who are signed up to receive prerelease builds on the "FAST" ring. For more information you can see this blog:
https://blogs.windows.com/windowsexperience/2017/06/21/announcing-windows-10-insider-preview-build-16226-pc/#hKj4174uBzOxpHTx.97
As I said this prerelease build has the fix to allow the Broadcom 440x to function as before. After we receive feedback from Windows Insiders to ensure that we are not breaking anything else we will look at including this in the Creators Update, which will go out to non windows insiders.
I still cannot promise any dates or releases. But this is a big milestone.
If any of you are windows insiders and have tried out this build let us know if it works or not. I have personally installed this build on a Dell Inspiron 9300 in my office, but it is great to get more feedback from the community.

Travis, I have clean installed Windows 10 Build 16193 from ISO. The machine has now upgraded to Build 16226

I can confirm the onboard Broadcom 440x NIC is working again.

The machine I have installed on is a Dell Dimension C521

spud17

Update.
Only an estimated 150,000 machines affected by the Broadcom issue.
This is the first Microsoft forum that I've seen to actually be helpful.
It also must be a first for Microsoft to take ownership of a problem, keep everyone informed, produce a solution, test it then release it.
Hats off to Travis at Microsoft.
https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/problems-with-creators-update/d5117f36-b66f-4590-b2f3-a64b92445385?rtAction=1492183836572

Currently the solution is only available from Windows Catalog (KB4032188) or via updates.
It will be rolled up into the Fall Creators Update.