[Rick CorbettAskWoody_MVP]

I’ve just carried out a clean install of 1903 (from an MCT-prepared USB stick) and thought I would demonstrate the SMB1 issue graphically.

The Win 10 default of *not* using SMB1 shows my current network as this (names hidden to protect the innocent… 🙂 ):

Compare this with a network view from a Linux Mint device (after Samba’s configured):

Now compare the same 1903 network view *after* SMB1 is re-enabled:

Note that this is *NOT* a 1903 issue… it’s the effect of turning off SMB1 by default due to very legitimate security concerns.

I could be wrong but 1903 appears to have introduced an SMB Direct ‘Feature’ (enabled by default) but this has done little to mitigate the effect of a reduced network view by default.

Hope this helps…

Attachments:

You must be logged in to access attached files.

[Rick CorbettAskWoody_MVP]

I tend to always do a clean install with new major versions. I’ve carried out several installs of 1903 now, all on laptops bar one (a Dell EliteDesk) and all of which were clean installs bar one. (All from an 8GB USB stick created by Microsoft’s MCT. None of them have balked at using this external device but I’ve been careful to yank the USB stick out during the first reboot.) Only one have I carried out an in-place upgrade on – a Lenovo ThinkPad x121e – and that was only because it had Office 2010 installed.

I’ve only noticed 3 issues with 1903 so far, two minor and the other annoying and very visible. The first was BgInfo misreporting the OS version. This was fixed after updating BgInfo. The second was after using an in-place upgrade rather than a clean install – the desktop icon order was re-arranged (alphabetically, IIRC).

The third is the desktop background not reverting on disconnect of a TeamViewer 14 remote access session. 🙁

(The default for TeamViewer is to remove any desktop colour scheme and/or bitmap in order to improve the speed of desktop refreshes to the remote client.) I’m still working on this one, hoping to be able to script my way around it or, if not possible, to change TeamViewer’s default behaviour. I haven’t notified TeamViewer yet ‘cos I’ve only just noticed the behaviour ate yesterday.

Before you do a clean install of 1903, have you tried turning off Win 10’s hybrid Fast Boot to see if that’s the issue? I’m not really fussed about boot times so always turn Fast Boot off… ‘cos I believe it gives more reliable startups without the issues you describe. (I have an old Dell 490 which just won’t won’t shut down properly with Fast Boot enabled.)

Hope this helps… (Guinea Pig 🙂 )

[Rick CorbettAskWoody_MVP]

Further testing with 1903 shows that the TeamViewer 14 ‘desktop redraw’ issue I mentioned earlier seems to be tied in to Intel graphic chipsets – a known issue, apparently… but not ALL Intel graphics chipsets.

I’ve just ‘TM’d’ into a Dell laptop using TM14 then – some time later – closed the TM connection. The remote TM server – a Dell Latitude E7440 laptop – has immediately reverted its desktop display back to normal on close of the remote TM14 connection. Device Manager on the laptop shows it uses a ‘Display adaptor’ from the ‘Intel(R) HD Graphics Family’.

The device which has an issue with the exact same scenario is a refurbished HP EliteDesk SFF which Device Manager shows as using an ‘Intel(R) HD Graphics 4600’ display adaptor.

(Can I just add a shoutout to TeamViewer for allowing free use of its product for personal use. Whilst the UK is tiny by comparison to other countries, this remote access tool has saved me travelling hundreds and hundreds of miles east and west to fix problems with my extended family’s IT needs. 🙂 ).

Hope this helps…

[Rick CorbettAskWoody_MVP]

Mele20 wrote:

Shame on Apple though for not making it clear and Microsoft for adding to the confusion.

I know what you mean but I wonder how much say Apple has in how its app is described in the Microsoft Store.

As it’s Microsoft’s Store, shouldn’t it be down to Microsoft to make it absolutely clear about what version is needed? Shouldn’t it be down to Microsoft to not confuse version with build? 🙂

I agree with you that the Store entry is confusing. For example, under Additional Info I clicked on the link for More:

What on earth does “This app can… Microsoft.classicAppCompat_8wekyb3d8bbwe” mean?

Why, if you click on the link for Permissions info, does it whisk you away from the Store completely, instead of opening in a new tab or window?

Why – if the app was apparently released 2 days ago (according to the Microsoft blog) – does the Store show the release date as 01/02/2019? 🙂

Attachments:

You must be logged in to access attached files.

3 users thanked author for this post.

doriel,

Mele20,

Nathan Parker

[Rick CorbettAskWoody_MVP]

barcud wrote:

I used the official download windows site to download the creation tool and create an install pendrive for 1903.

I did *exactly* the same as you and also got 18362.30. A ‘Check for updates’ installed KB4497936 – like you – on 21st May. A subsequent ‘Check for updates’ yesterday installed KB4503293, taking the build up to 18362.175:

Perhaps do a manual ‘Check for updates’?

Hope this helps…

EDIT: Oops… OP beat me to it. Glad it updated OK.

Attachments:

You must be logged in to access attached files.

1 user thanked author for this post.

barcud

[Rick CorbettAskWoody_MVP]

Mele20 wrote:

You should have mentioned that 1903 is required for this version of iCloud for Windows.

The OP is referring to an article posted on MacRumours. In that article there is no mention that 1903 is required. Instead, it refers to “according to a blog post shared by Microsoft).

The MS blog post doesn’t mention that 1903 is required either… but provides a link to the iCloud app in the Microsoft Store.

The app’s Store entry doesn’t specifically mention that 1903 is required. Instead, the System Requirements show that “Windows 10 version 18362.145 or higher” is the minimum requirement.

Forgetting for the moment that ‘18362.145’ is actually the build (and revision), *not* the version – how many people know that this info actually means version 1903? I had to look it up to check. 🙂

1 user thanked author for this post.

Nathan Parker

[Rick CorbettAskWoody_MVP]

A final post on this topic… I had another email from the University of Kent’s mirror service asking if the PC in question was up-to-date. Well, nearly so… I was aware that MS had released an update to the root certificates at the beginning of April so I had installed the security updates at the time but not updated since.

However, a Google search for win 7 certificate store turned up a TechNet article – Trust root certificate store is not updating – about this April update failing… so it was apparently re-issued. I checked Windows Update (mine’s set to manual, not automatic) and ran in the 2 available security updates (KB4474419 and KB4503292), restarted then tried to update from VLC 3.0.7 to 3.0.7.1 using its internal updater. Success – no errors! 🙂

2 users thanked author for this post.

BATcher,

satrow

[Rick CorbettAskWoody_MVP]

I received a very helpful email from help@mirrorservice.org in reply:

The message says the certificate is not trusted which means the root
certificate is missing from whatever list that VLC is using. Maybe it
has its own internal one, or maybe it’s an OS level one, but in any case
the root certificate for the certificate provider we use is obviously
not there.

I don’t think there’s a lot we can do about this. It’s a system based on
trust, and we use a widely used provider so it should be supported
everywhere. We also haven’t had any other reports (I think recall seeing
it for VLC before, though) of problems. So I’m inclined to suggest this
is VLC specific problem.

If you’re worried just download the latest version directly and install
it, rather than using the builtin updater.

This got me thinking so I installed VLC 3.0.6 in a Windows 7 Home Premium VM and tried to update using its internal updater.

The first attempt produced an error:

However, a second attempt was successful (and downloaded v3.0.7.1 from get.videolan.org).

I’m inclined to think it was just an issue with my main Win 7 PC. I’m not going to do any more digging into the cause now I know I’m the only one who had an issue with the University of Kent’s mirror service. (Kudos to the support team there for the informative and speedy response to my email.)

Hope this helps…

Attachments:

You must be logged in to access attached files.

[Rick CorbettAskWoody_MVP]

Thanks to @skiph for the info that SMB1 wasn’t enabled in his home network.

Following the post I switched on a laptop running Win 10  Pro 1809, thus making it the 5th device up and running in my own home network… but I could only see one other Win 10 device and my main Win 7 Pro PC… even though both SMB1 client and server protocols were enabled on the laptop I had just switched on.

I checked the other devices and they could all see each other… and the new laptop. I returned to the laptop to check again and found a weird anomaly… the laptop  was displaying all 5 devices in the left-hand navigation pane but only 3 devices in the right-hand pane. I left it several more minutes and checked again… and now the right-hand pane is showing all devices.

I’ve noticed similar before, i.e. if I start a new Win 10 VM then it sees other Win 10 and Win 7 devices but it will only connect immediately to shares on the Win 10 devices. I have to wait several minutes before I’m also able to connect to shares on my Win 7 PC.

So now I’m wondering why time is important (or is the delay because the laptop is the only device connected via wireless and the rest all use ethernet?).

It will be interesting to hear how the OP gets on. In the meantime I’m going to start checking the services that @skiph mentions in his other post. 🙂

[Rick CorbettAskWoody_MVP]

In my experience this network ‘view’ issue is not limited to the latest 1903 version nor to just Home editions. It just depends on whether SMB v1 (client and server) is turned on as a Windows feature.

For example, in my home network my Win 7 main PC can see all 4 devices currently up and running. My Win 10 Pro 1903 can only see 2, my Win 10 Home 1803 can only see 2 but my Win 10 Pro 1709 can see all 4.

On the Win 10 devices which can only see 2 others, if I turn on SMB v1 (client and server) and restart then they can see all devices.

As I’m within a home network I’m happy to have SMB v1 active.

It’s very easy to check the status using PowerShell in Win 10 (any edition/version):

1. *Right*-click on Start.
2. Choose Windows PowerShell (Admin).
   (for older versions, choose Command Prompt (Admin) then enter powershell to get the same PS prompt)
3. At the PS prompt, enter get-windowsoptionalfeature -online | where featurename -like *smb1*

This will show you the status of SMB1:

To stop any restrictions on network ‘view’ you can also re-enable SMB v1 using PowerShell:

 Enable-WindowsOptionalFeature -Online -FeatureName “SMB1Protocol”

This is the ‘parent’ feature and has to be carried out first. You’ll be asked whether you want to restart. Enter n for No then enter the following:

Enable-WindowsOptionalFeature -Online -FeatureName “SMB1Protocol-Client”

Enter n for No again then enter the following::

Enable-WindowsOptionalFeature -Online -FeatureName “SMB1Protocol-Server”

Now restart the device.

Hope this helps…

Attachments:

You must be logged in to access attached files.

1 user thanked author for this post.

WSraysig

[Rick CorbettAskWoody_MVP]

Have you ever used this? I have … and won’t use it again. Darn, it’s amazingly slow.

It’s much, much faster to restore from, say, a Macrium Reflect disk image.

[Rick CorbettAskWoody_MVP]

Thanks, @Zig, for the info that SMB Direct is present and enabled in 1809. I didn’t have any 1809 devices available to check.

[Rick CorbettAskWoody_MVP]

I just checked the direct download for VLC 3.0.7.1 (x64) installer with VirusTotal and MBAM Premium and it comes up clean.

2 users thanked author for this post.

jburk07,

Bill C.

[Rick CorbettAskWoody_MVP]

Did you happen to notice whether the update came from get.videolan.org or was it from somewhere else? Does MBAM say what type of exploit?

Perhaps restore the installer from Quarantine then check it using VirusTotal?

Hope this helps…

1 user thanked author for this post.

Bill C.

[Rick CorbettAskWoody_MVP]

Many thanks for this. I found the script – DisableUnusedSmb1.ps1 – in a sub-folder of C:\Windows\WinSxS. By default, only TrustedInstaller has full control over it so I wasn’t able to just rename it or append _old to it. I also went through Task Scheduler but didn’t spot anything that actually triggers the script.

I did find this MS article SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions which includes:

Automatic removal of SMBv1 after 15 days is a one-time operation. If an administrator re-installs SMBv1, no further attempts will be made to uninstall it.

[Author]

Posts