Windows 10: Generic Roaming error ID3

Someone wrote here that Windows updates are increasingly behaving like viruses. I won't go that far BUT recently each update brings a host of errors to an otherwise well functioning computer (16mb ram; i7 4930k; win 10 professional with all updates).

The latest is the Generic Roaming Error ID3.

Here is the header from the error message:

"There was an error while applying setting unit 7375A7CC00C60758CC303261DF9E1A852E993C7D for roaming collection Windows-Credentials. The parameter is incorrect."

I don't have a clue what this is about.

Does anyone??

Thanks in advance.

:)

 

5230 can not see the directly copied MP files

*Solved*



I converted to MP3's to various formats, but nothing seems to help.

They can be transferred to system, if to memcard, the player won't see them. If to inbox, they can be played, but during save Generic system exception



The error saving, led me to think some kind of bug in years ago in nokia phone with scandic letters in filenames (mp3s). This one didn't have those, but the MP3s did not have ID3 tags at all!



I added title and artist ID3 tags to original MP3 to the phone

id3tool -t title -r artist file.mp3

(or in Windows 7 right click mp3 and edit the fields)



Plugin 5230 via USB, select media transfer. For me..Windows Media Player started, drag and dropped files there, synced and worked!



Also via bluetooth/inbox save works if MP3 files have ID3 tags (artist or title may be either one will suffice). Without ID3 it crashes.

 

Event log for Fall Creator:

I receive error event ID 3 Generic-Event Tracing/Admin, There was an error while applying setting unit 0C5E59758D022979DE8B20D31C530A24A3E00318 for roaming collection Windows-Credentials. The parameter is incorrect, it has created 1952 errors in the last
hour

 

Please check the following case for assistance.



Error 3 GenericRoaming error



http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/error-3-genericroaming-error-in-event-viewer/f3547315-4f99-4220-8d69-39420c5f7845?page=1

 

Thank you. Unless there is a simpler fix, which will allow me to keep my system untouched (because it is stable despite this and other errors), I'll wait for the next couple of updates to see what happens.

My last serial update attack (Event ID 2 (session Microsoft.Windows.Remediation not started) was resolved with updates and no action on my part.

Fingers crossed.

 

The simplest suggestion was to turn off syncing among machines to kill the error, which I did in upstate New York (Windows Settings, Accounts, Sync Your Settings) on my computer there.

Came back to Brooklyn late morning and did the same (turn off syncing) to an identical machine (same hardware, same build from image).

The Brooklyn machine then proceeded to update itself to the October 1709 even though that was already on the computer. Afterwards it did other updates.

Can't figure out what is wrong (if something is wrong). Why did Windows Update the machine that already has the updates.

Strange, strange.

Any hypotheses welcome. Thanks.

 

Windows OS should not install same updates twice maybe update you mentioned failed to install first time.