KB5032278 Windows 10 Cumulative Update Preview Build 19045.3758 (22H2) Win Update

Hi guys..
Is this feature risky to use or safe to get updates early..?
See screenshot..
Thanks in advance.
Banyarola

Thank you...I will leave it off.
The 2278 preview already installed so I will disable Co-Pilot when the update installs...
I'm not even sure what CoPilot is but I will disable it.
Once again, thank you for your response...
Banyarola

I'm not even sure what CoPilot is but I will disable it.

Co-pilot- AI feature being added by MS that few seem to think well of.
(Latest incarnation of 'Hey Cortana, tell me a joke' etc.. but meant to be more informative and functional, I guess).

Feel free to search tenforums etc. E.g.
Continued AI Innovation in Copilot

I don't think it is only KB5032278 causing the event id 131 Device Setup Manager Metadata staging failed. I haven't updated since mid October and did KB 890830, KB5032339, KB5032189 and KB4023057 today and on reboot after update I started getting many of the event id 131 Device Setup Manager Metadata staging failed. I would get the code 131 when plugging in my backup USB external. Even when using USB thumb drive- this never happen prior to today's update.
I got to looking at the registry for devicemedadataserviceURL. I went to that URL (go.microsoft.com/fwlink/?linkid=252669&clcid=0x409) and got redirected as site not available to dmd.metaservices.microsoft.com where I pressed continue and got a 505 Bad Gateway error.
And then just for the heck of it I did a DISM with /checkhealth and all was good, did DISM with /scanhealth and it said all was fine. Even did sfc /scannow and chkdsk, all was well.
Then I did some thinking (which can be dangerous) Booting or adding external drives got many of the 131 errors. However when I disconnect from the internet and boot or add external drives- I GRT NO ERRORS 131.
Between all this, I believe our friends at Microsoft have a bad pointer. in the registry entry devicemedadataserviceURL.
I did an image of system prior to update, thought about restore and still considering. All is working fine, I tried all devices and all are working. I shouldn't look at that event log! I haven't run KB5032278 as it's optional and as I said I still just today aftter the mentioned updates started getting these errors. Maybe the pointer is correct, but MS has a website link issue? Don't know how to tell them, doubt they would listen.
I should add going to control Panel, search for Device Installation, select change device installation setting to NO- does fix the error. Tested, reboot or adding external drive no longer gets the 131 error. Now is this a good idea, I don't know, I am not that up on computers anymore. I retired in 2003 after 38 years as system software tech on mainframes. Was certified also for Microsoft, but a lot changed since then and I really don't attempt to keep up.