Cumulative Update KB4487044 Windows 10 v1809 Build 17763.316 - Feb. 12 Win Update

@Bree

no probs on XP but W10 is broken - at least on my system. XP connects as "Z" in this case folder Audio.

XP version :



You can see the folder Audio is shown as Disk Z

On my W10 the browse is greyed out ??? Folders have Read Write access so not permissions problem. W10 can connect to whole drive. File explorer defect -- ? I know there were a load in the insider builds but this is standard Windows with latest updates. HDD0 is a clone of HDD2 with correct SAMBA config file so it should map identically as HDD2 with folders etc to "Y".

W10 version:



Cheers
jimbo

IronZorg89 said:

Most welcome!. Really hoping that you can find a solution to installing this CU with no hiccup.

I restarted the PC again and lo and behold, it has now updated. Very weird indeed.

jimbo45 said:

...On my W10 the browse is greyed out ???

Ah, you are starting from the wrong place.

Both XP and W10 behave exactly the same way. When you right-click on the share itself and select 'map network drive...' the browse box is pre-populated with the name of the share and the browse button is greyed out. Here it is greyed out in XP....



But if you right-click on 'This PC' in W10 or 'My Computer' in XP and select 'map network drive...' from there you can browse as much as you want....

Bree said:

Ah, you are starting from the wrong place.

Both XP and W10 behave exactly the same way. When you right-click on the share itself and select 'map network drive...' the browse box is pre-populated with the name of the share and the browse button is greyed out. Here it is greyed out in XP....



But if you right-click on 'This PC' in W10 or 'My Computer' in XP and select 'map network drive...' from there you can browse as much as you want....

Hi there

Probably never noticed what I was doing before

Anyway thanks !!!

Cheers
jimbo

jimbo45 said:

Hi there
Probably never noticed what I was doing before
Anyway thanks !!!
Cheers
jimbo

Mooly said:

I restarted the PC again and lo and behold, it has now updated. Very weird indeed.

Very weird indeed, to say the least. This one, there is nothing I can think of to explain it. Probably, something hogged the Windows Updates process and that's why when something unexpected happens, it is always recommended to restart the system first to see if it will go away. Sometimes this works and sometimes it does not.

Anyhow, the most important is that you are up and running normally. that's what counts. Cheers!

Yes, it was very odd because the failure message in my case said it related (apparently) to the account I was signed in with... which with a local account is a bit weird. It got there in the end though.