![]() ![]() Please see pages 2 and 3 onwards in this forum: I am not getting Event ID 131 anymore as well. After that I did not get any more 131 errors. In regards to the event id 131 for Windows 10, I went to control panel, devices and printers, right click your pc icon, click device installation settings, click no let me choose what to do, uncheck box automatically get the device app and info providedīy your device manufacturer. I don't have any problem with them neither. My W 8.1 partitions are both local users and I am an Insider, so MSA is mandatory, so I can't speak directly the MSA concerns but I can say that I am not having any Driver issues and am getting new Drivers when they are available, if they are necessary. I have had these problems myself on occasion but nothing consistent. I do know that WU has problems getting updates and drivers to some users for a myriad of reasons as well as the right type and version. I don't believe MS is blocking any WU activity since that would be completely opposite to what they are trying to accomplish. Is Microsoft intentionally blocking users not using "Microsoft Accounts" from Windows Updates? I do not want Microsoft tracking my internet activity, so I will only use this "Microsoft Account" to execute Windows Updates. I added a Hotmail "Microsoft Account" and used this account to perform Windows Updates and I no longer get these errors. ![]() I use local user (administrator) accounts, not "Microsoft Accounts", to login to my computers. I had the same errors and devices were not getting updated drivers. I am going to "Unanswer" the Former Answers. Even though I did not have an issue in Windows 8.1 Pro, I changed them too, as a preventative precaution. Right Click with mouse on any blank spaceįinally a real answer to this long term problem. Since I am in the North West I chose accordingly as follows: I can attest that this does work the why the Meta System was suppose to work in the first place! Set everything back to the why Microsoft Recommends and change the Time Updating Source. The time server is obviously correct to the millisecond and the window time server is not! Your system should now be error free: I have tested this by refreshing all hardware devices etc. Amtino on the "Microsoft Community" wrote on this Subject:Ī new resolution to the issue without changing the url in the registry or touching anything we shouldn't really:Ĭlick on time and date at bottom right of screen.Ĭhange the server in the drop down list from windows time to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |