Watch out for the Cumulative rollup update for 1703 - already!!!

I got brave (foolhardy) and decided to have another go at upgrading the existing laptop to Windows 10 from Windows 7.  It was pretty stress free - I am impressed so far.  I have version 1703 and its fast (so far, touch wood, fingers crossed)

Couple of odd teething troubles with email, and the internal microphone on the laptop has vanished completely from the system, but apart from that, so far so good.  And to my enormous relief it has preserved my old Windows 7 desktop as the first thing I see on log on, and the bewildering windows 10 boxes only appear when I use "start"

I'm beginning to wonder if I needed that new laptop - all my latency issues seem to be fixed. 

Thanks Martin

I had already had a good look at device manager and tried updating some drivers - all appear to be (are claimed to be) up to date.  There are no unknown devices listed.  Curiously the webcam, which is physically next to it , is not showing either, but works via a cam utility

I have also lost the floating next page bar on this forum on Firefox

Still mostly good though

I haven't plugged one in yet, because all my mikes have XLR leads - but I would expect it to work.  Device manager can see the mic socket on the laptop, and the mic socket on the Kensington docking station, and it knows there are no microphones plugged into them - but it can't see the in-built mike.  I could get a mike, and might do- but I have a new laptop arriving any day now, and this one will be retired to "backup"

It's never a daft question when you're trying to help someone Paul.
I can use the sound manager to set a default mike.  Both of my available options are currently greyed out because I have disabled them.  They are the socket on the front of the laptop, and the socket on the Kensington USB docking station.  I can enable either or both, and any test points out that I don't have a microphone plugged in.

There is also a tiny pinhole mic built into the lid next to the tiny webcam (which also doesn't show as a device - but works).  The pinhole mic doesn't show and doesn't work (with Cortana anyway)

TBH its not the big problem.

The two remaining issues are

1)Losing the tiles on the taskbar on reboot and having to restart Windows Explorer manually from the Task Manager to fix it
2) Losing the ability to scan duplex with my brother DCP9045CDN from Paperport 14 although I have uninstalled the old drivers and installed Windows 10 drivers, and reconfigured the TWAIN driver and everything else works.  A hint as to what may be going on is that during the TWAIN set up the program reports that the scanner is not physically connected when it is.  It then goes on to properly (nearly) configure the device it has just reported isn't physically connected.  Maybe there's something wrong with a plug and play detector

I'll hope to get the new laptop up and running and fully functional, and then I can have another go at this one without risking losing it when I need it for work

(My floating page bar on TAS is back. )

Well, I've just installed the Creator's Edition (1703) and it took it's sweet time. I always worry when Windows takes what I consider to be "too long" (my machine is no slouch - i7-4770 3.4GHz with 32Gb of memory) to perform an action but it got there eventually.  One major "this is why Micro$oft pisses me off" problem.  I use a third party firewall.  Telling me that I should use Windoze security will not negate the fact that the update not only deleted my Private Firewall installation but when I'd re-downloaded it and then tried to install it lo and behold there was a policy set to stop it installing.  A quick trip to regedit sorted that out but why on earth should I have to do that?
Also, unlike before, I cannot now shut down the Windows Firewall service from the Services panel in Administrative Tools.  I've set the startup type to manual but it starts anyway.  When I right-click the service and hit "Stop" it throws up an error message telling me that...


Sussed it.

It turns out that I had to disable the service before I could stop it.  How intuitive...NOT!  I've now set it to Manual as I had it set before the update but I'm still wondering if it will auto-start anyway the next time I reboot the system.

Other than that, it all seems to be working OK, but it's early days yet.

I use Bitdefender.  The upgrade from Windows 7 to 10 (1703) was long but trouble free and has left everything (apart from the minor driver issues, and the email account protocols) untouched. Bitdefender firewall is still operating and attempts to turn on or off the Windows version are blocked with a message that Bitdefender is currently managing these

I have yet to do anything more than charge the battery on the new machine...

Just a footnote. Despite stopping the Windows Firewall Service and setting it to Manual Startup type it started running on bootup today. I've now disabled it in the Services tab. I know it's not critical but I don't want two firewall services running when there's no way of checking if there are, or could be in future, any conflicts.

A couple of weeks on with the W10 insider / early adopter programme on our 640 phones, on the safest of the three options and all is well.
I've had a couple of updates, reported a few bugs and in general its all good.
At least it has Facebook messenger I still can't get WhatsApp to work ok Marie's 640. Inexplicable!