Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9

Caledon Ken · 11 Oct 2018

Ciantic said:

You mean this KB4464330 was also pulled? What on earth. On my machine the Windows Update keeps trying to install it, the Windows Update dialog downloaded it twice already, even without my help.

Maybe I shouldn't bother trying to install that. They will come up a new one in time.

I went back and found reference to it being paused... Kado posted back in post #125

https://answers.microsoft.com/en-us/...b6766c9?auth=1

See the highlighted blue text.

IronZorg89 · 11 Oct 2018

Caledon Ken said:

I went back and found reference to it being paused... Kado posted back in post #125

https://answers.microsoft.com/en-us/...b6766c9?auth=1

See the highlighted blue text.

So, it's no use trying to install any update at this point for now. And @Ciantic, you are better off pausing updates for a while or put yourself on metered connection until all this mess is sorted out.
There are so many contradictory informations going on out there:
- According to an excerpt from a zdnet.com's article:
In a tweet, Dona Sarkar, who runs the Windows Insider Program, advised anyone affected by this issue to call Microsoft's support lines: "They have the tools to get you back to a good state." The implication in that tweet (and in the language from the original bulletin) is that the files have not been deleted but are available elsewhere on the system disk.

-In another article from ghacks.net with regard to the deleted files after the update to 1809:
An administrator who manages a PC affected by the issue suspects that
the issue is caused by the Group Policy "Delete user profiles older
than a specified number of days on system restart" in Computer
Configuration > Administrative Templates > System > User
Profiles as it was set on the device and not on others where the issue
was not experienced.
Whether the policy is indeed responsible has not been confirmed yet.

By and large, at this point it's a good policy to wait and see.

katlani · 11 Oct 2018

Anyone knows what does the Guest option mean when i click on my username for logging off in the start menu?
I dont remember having that before and suddenly i have a Guest clickable option.

I'm using a local account.

Bree · 11 Oct 2018

katlani said:

Anyone knows what does the Guest option mean when i click on my username for logging off in the start menu?

It means the built in Guest account is set as Active. When you click on your user icon on Start you see all active accounts listed there. Normally on a machine with multiple accounts you can click on another name in that list to switch to signing in as that user without signing out of your account.

You can see a list of all accounts, active or not, in a Command Prompt (Admin) with the command NET USERS and see the details of each account with NET USER USERNAME which in the case of Guest shows it to be Active.

Cumulative Update KB4464330 Windows 10 v1809 Build 17763.55 - Oct. 9-image.png

I dont remember having that before and suddenly i have a Guest clickable option.

No, I don't remember seeing it before either, but I've just checked on a system still running 1803 and it's there too.

However, despite being active in 1803 or 1809 seems you can't sign in as Guest.

katlani · 12 Oct 2018

Thanks Bree. So what do you make of it? Another feature microsoft have not tested?
How is it there all of the sudden? Maybe latest CU enabled it?

Will it be safe to make it inactive? Couldn't find a UI way to do so, only cmd prompt way which I haven't tried.

tomseys · 12 Oct 2018

Did you guys deliberately set guest to active or enable it in some way?

katlani · 12 Oct 2018

Not that I'm aware of..

tomseys · 12 Oct 2018

I see.. mine is set to active = "no" and I don't have that guest choice in 1803.

Mooly · 12 Oct 2018

KB4464330 is still found by WU as of 8:30AM GMT when running a manual check.

Ciantic · 12 Oct 2018

Mooly said:

KB4464330 is still found by WU as of 8:30AM GMT when running a manual check.

I don't see any news about it being pulled. One would think the Thurrot or Windows Central would have blown in the whizzle by now. It would be too good story to not report about, think about it: They pull the update KB4464330 of the pulled update 1809.