Windows 10: WIN CU 1703 doesn't find Toshiba A105 laptop devices

I think my A105 Satellite is a victum of microsoft's support cutoff of older Toshiba laptops. CU doesn't find some of the laptop's devices. I've managed to get the problem display and USB devices working, but I've not been able to fix or find usable drivers for the ethernet, wireless and SD card reader.

Has anyone found a solution yet?

Ethernet : Intel PRO/100 VE
WiFi: Intel PRO/Wireless 3945ABG
Chipset: Intel 945 Express

:)

 

My Current Upgrades

Added the below:

A home built Tower with a E8400 dual core, 8 gigs of ram updated from Win7 Pro to Win 10 pro 64 bit

Lenovo T-61 laptop

A Toshiba A105-S484 laptop.

After updates with Win 10 and Waterfox as is well with Waterfox

 

Still no creators update

I have a Toshiba Satellite P50-C-12z (PSPTSE) laptop running Win 10 1607.

I have never been offered the 1703 update.

I am aware Toshiba's had an issue with a display utility which I have now uninstalled.

Now in November I am still not being offered the 1703 update, I can no longer even manually trigger the 1703 update as it has been replaced by 1709.

I don't want to manually trigger 1709 if there is a possibility my laptop is incompatible.

Toshiba's compatibility lists don't include my Laptop, but then it doesn't include it for 1607 either so its not very reliable.

Will I ever get the 1703/1709 update?

I am getting nervous that my laptop will be obsolete in March 2018 if 1607 support ends as planned and I can't upgrade.

It is only 2 years old so I will not be impressed.

 

This is a thread from 2016, it may help for the WiFi....

Intel PRO/Wireless 3945ABG Windows 10 |Intel Communities

If you follow its link to the Intel download page note that it says there's a newer version now.

 

Thank you. The wireless worked fine after I upgraded from WIN7 to WIN10. It stopped working with the update from 1607 to 1703. I've tried the newer intel driver (19.n) version and an older (17.n) version, but neither one worked. I have not tried an 18.n version. I'll give it a try.

 

No luck either. I guess the fallback maybe external USB Ethernet and WiFi adapters.

Maybe I should be asking the question differently: Is anyone using a Satellite A105 with WIN10 1703 and their Intel networking devices work okay? If so what drivers are you using?

 

Not according to Google, as far as I can make out... *Sad

Do you make system images with Macrium or similar? D you have an image of the working Anniversary Update (1607) from before your upgrade to Creators Update (1703)? If so, you could restore it and export your previously working drivers. Then you could try importing them to the current system. If that works, you'd need to disable any further driver updates.

Backup and Restore Device Drivers in Windows 10
Enable or Disable Driver Updates in Windows Update in Windows 10

If you don't have a suitable system image available, you could make an image of the system as it is now then try a clean install of 1607. If that has working Ethernet/WiFi, export the drivers, restore your current system then import drivers as above.

It's still possible to get an ISO for the Anniversary Update direct from Microsoft. Go to Microsoft's Download Windows 10 page using Edge. Now use the F12 Developers Tools and on the Emulation tab set the 'User Agent String' to 'Apple Safari (iPad)'. The page then changes to one offering direct ISO downloads.

 

Thank you again. I have reverted to 1607. I didn't think of reusing the 1607 drivers on 1703. Good idea.

My Google searches found problematic issues with circa A105 laptops, but not many. I did find several tech'ie references to 1) the fact that the A105 isn't compatible with WIN10 but can be made to work (as I have in the past), 2) 1703 has removed support for it's drivers, and 3) 1703 has changed the way WIN10 supports the ACIP tables. The internet being what it is, who really knows what to rely on; however, your idea is the best one anyone has come up with so far. Definitely worth a try.

 

Oh good, you had a system image. That's a relief. Now you have some breathing space to investigate further. If it turns out 1607 is the highest you can go, then you can hide Features Updates like 1703 from ever installing. Pro's 'defer upgrades' can only hold back the tide for a limited time, but hiding them is a permanent block. I use this on my test machine for each of its earlier system images to stop them upgrading themselves.

Hide or Show Windows Updates in Windows 10

 

Have you tried these? They worked for me on 1607 Home:

// Stop ethernet updates
Change:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost
From:
Ethernet DWORD 1
To:
Ethernet DWORD 2

Add key and DWORD subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
AUOptions DWORD 2 (Notify for download and notify for install)
3 (Auto download and notify for install)
4 (Auto download and schedule the install)
5 (Allow local admin to choose settings)

// Stop wireless update
Settings>Network & Internet>Wifi>Manage known networks
Select a wifi network
Click on Properties
Set Metered Connection: ON

 

Setting a metered connection stops all updates. Yes, it will stop a Features Update, but at the cost of never being able to get any cumulative updates. You cannot pick and choose. Once you click the 'download' button you get when checking for update on a metered connection they all start downloading, including the Features Update.

Hiding just the Features Update let's you continue to get cumulative updates. Your PC would be on 1607 for as long as the Features Update is hidden, but continue to stay up to date.

I use my test PC for investigating support questions in this forum, so I don't want to change the registry setting for Windows Update from their defaults. It has images for all versions of Pro from 10240 up to 1709. I want to keep each version up to date. The only way I can check for updates without triggering an upgrade is to hide the Features Update. Pro's 'defer' option only goes so far, as soon as a version becomes Current Branch for Business (or Semi-Annual Channel as it is now known) it is declared as ready for widespread use in organisations and can no longer be deferred.

 

Yea, you're right. But if you're using a system for which MS has discontinued support, the problem becomes that each time there is a new major update there is also the chance that the new update will crash an older systems they no longer support. The only solution to keep that system functioning is to return it to the prior version that worked. BUT - after that, each time a new cumulative update is issued, the automatic installation process it will again make the system unusable.

Not to start rumors, but one of the sites I found said that MS is seeing an increasing number of returns to a prior version and has realized the problem; and, they are considering ways to block future updates on systems that cannot be successfully updated. For example, (like in my case) if a system works on 1607 but crashes on 1703, returning it to 1607 will stop future updates to prevent the problem from reocuring. Like I said, don't believe everything you see on the internet.

In conclusion, I want to give you a special thanks for the role you play in this forum. I cannot tell you how much benefit I get from TenForums and it's people like you who make that all possible. You really do make a difference.

 

Already seems to have happened for Clover Trail/Intel Atom PCs.

http://www.zdnet.com/article/microso...ver-trail-pcs/

Thanks for your kind words.

 

Reversion to 1607 was the solution (except the SD card reader which doesn't work). This link confirms the MS cutoff and tells how to block future updates that try to reinstall the update that wasn't compatible.

How to Block a Windows 10 Feature Update and Why You Might Need To