,Japan

en[EVENT200] Could not establish a connection to the Windows Update service
After updating to Windows 10 v1903, [Event ID 200] is recorded in the event log.
The message is as follows.
Could not establish a connection to the Windows Update service.
I suspect that this log may have been recorded due to the Wi-Fi connection being cut off when Windows 10 wakes from sleep.
It's a warning level, so it's best to ignore it, but you have the following options:
[Choice]
- ignore
- Prevent from being recorded in the event log
- Modify the data of DeviceMetadataServiceURL
Well, the main subject.
This article describes options B and C.Option C is
It is effective for Windows 10 where [Event ID 200,201,202] is recorded.
And it was written online ...?
Event Log
The event log is reprinted.message | Could not establish a connection to the Windows Update service. |
log name | Microsoft-Windows-DeviceSetupManager /Admin |
Source | DeviceSetupManager |
Event id | 200 |
level | warning |
user | SYSTEM |
Guid | {fcbb06bb-6a2a-46e3-abaa-246cb4e508b2} |
Repair procedure
Registry operations are at your own risk
Before working with Registry EditorMake a backup copy of your registry in case something goes wrong.
To start Registry Editor:
- Start the execution by specifying the file name ( Field (Win) + R )
- Type regedit in the box next to your name
- OK Click on the

Option B
This is a procedure to prevent recording in the event log.- Start Registry Editor
- Move to the next layer
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2} - Change to Enabled = 0 (default value: 1)
- Restart Windows
- End of procedure

Option C
This is the procedure to modify the data of DeviceMetadataServiceURL.- Start Registry Editor
- Move to the next level
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata
- Modify DeviceMetadataServiceURL data to http://dmd.metaservices.microsoft.com/dms/metadata.svc
- Restart Windows
- End of procedure
Before: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409
Afterword
According to me,The URL registered in [DeviceMetadataServiceURL] returns "HTTP ERROR 400" when accessed, but the problem has been pointed out since around 2016.
That means
As of July 2019, Microsoft has registered an invalid URL in the registry database.
...? ? ...
According to the writing of Windows 10 Forums, the procedure to fix DeviceMetadataServiceURL is effective for the PC with EVENT-ID 200, 201, 202.
If you want to refresh the event log, why not try repairing it?
Tracking information
2020/01/17Revalidated the URL related to DeviceMetadataServiceURL.
When you access the modification URL (option B) described in this article, 400 ERROR is returned, but if the event log recording stops after the modification, it means that the function is working.
If it doesn't improve, return it to the default value.
[result]
- Default value is redirected
- Redirect URL returns [400 ERROR]
- Modified URL returns [400 ERROR]
- ... would you fix it?
Division | URL | result |
Default value | http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 | redirect |
redirect | http://dmd.metaservices.microsoft.com/metadata.svc | 400 ERROR |
Modification URL | http://dmd.metaservices.microsoft.com/dms/metadata.svc | 400 ERROR |
HTTP ERROR 400
http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409(→ http://dmd.metaservices.microsoft.com/metadata.svc)
Transcription
This page is not working
If you continue to encounter this issue, contact the site owner.
HTTP ERROR 400

Validation: Windows 10 Pro May 2019 Update, v1903.18362.207
en-event の記事 (Articles about the en-event)
- Windows 11 22H2 and the event log (tak)
- en[EVENT131] Metadata staging failed
- en[EVENT7009] Service Control Manager (SCM)
- en[EVENT2484] Tile Database Corruption
- en[Event ID 10016] How to fix PerAppRuntimeBroker error
- en[Event3] Kernel-EventTracing Microsoft Security Client OOBE
- en[EVENT2002] Eap method DLL path
- en[EVENT333] ESENT error (taskhostw, WebCacheV01.dat)
- en[EVENT10016] Windows.SecurityCenter.WscBrokerManager, APPID not available
- en[EVENT34] Cancel power saving setting of power management of Bluetooth HID device
- en-event ラベルの記事(要約付)
- Japan が含まれる記事(要約付)
新着順 (New arrival order)
- 【緊急】KB5063060配信開始:Easy Anti-Cheat搭載PC向け自動適用の理由とは
- 【考察】藤井聡太との死闘が残したもの──タイトル戦はトップ棋士の試金石(トラウマ)
- 【VAIO】BIOS R0500K9リリース:Windows 11 24H2対応と脆弱性修正の詳細(2025年06月11日)
- 【Pixel/2025年6月】Android 16と指紋認証、Bluetooth、カメラ、システムの改善と修正
- 【盛者必衰】四段経験なしで全棋士を統括?清水市代新会長誕生が将棋界にもたらす衝撃と期待
- 【Windows 11】24H2 アップデート後のトラブルシューティング(DISM, SFC, コンポーネントサービス)
- Intel(R) ME Firmware Ver.11.8.97.4739(2025年6月3日)【vaio】
- 【Clibor】行頭に連番を挿入する方法【New!】
- 【ブログ執筆者必見】Cliborでテキスト整形をマスター!コピペ効率を劇的に上げる方法
- 吉田栄作と織田裕二:キャリアパスの分岐と戦略的選択の分析
タイトル:en[EVENT200] Could not establish a connection to the Windows Update service:SC2
このサイトを検索 | Search this site
0 コメント