product:getKnownIssuesByTimeRange

命名空间:microsoft.graph.windowsUpdates

重要

Microsoft Graph /beta 版本下的 API 可能会发生更改。 不支持在生产应用程序中使用这些 API。 若要确定 API 是否在 v1.0 中可用,请使用 版本 选择器。

根据过去的指定时间范围获取与特定产品相关的已知问题。

权限

为此 API 选择标记为最低特权的权限。 只有在应用需要它时,才使用更高的特权权限。 有关委派权限和应用程序权限的详细信息,请参阅权限类型。 要了解有关这些权限的详细信息,请参阅 权限参考

权限类型 最低特权权限 更高特权权限
委派(工作或学校帐户) WindowsUpdates.ReadWrite.All 不可用。
委派(个人 Microsoft 帐户) 不支持。 不支持。
应用程序 WindowsUpdates.ReadWrite.All 不可用。

重要

在具有工作或学校帐户的委托方案中,登录用户必须是组的所有者或成员,或者分配有受支持的Microsoft Entra角色或具有支持的角色权限的自定义角色。 Intune管理员Windows 更新部署管理员是此操作支持的最低特权角色。

HTTP 请求

GET /admin/windows/updates/products/{id}/GetKnownIssuesByTimeRange(daysInPast={daysInPast},includeAllActive={includeAllActive})

查询参数

下表显示了必须用于此函数的参数。

参数 类型 说明
daysInPast Int32 过去要查找的天数。 此筛选器将应用于处于最终状态且具有解决日期时间的所有已知问题。
includeAllActive 布尔值 如果设置为 true,则响应包括所有活动的已知问题。 如果设置为 false,则响应不包括任何活动已知问题。

请求标头

名称 说明
Authorization 持有者 {token}。 必填。 详细了解 身份验证和授权

请求正文

请勿提供此方法的请求正文。

响应

如果成功,此方法在 200 OK 响应正文中返回给定时间范围的响应代码和 microsoft.graph.windowsUpdates.knownIssue 对象的集合。

示例

请求

以下示例显示了一个请求。

GET https://graph.microsoft.com/beta/admin/windows/updates/products/1/GetKnownIssuesByTimeRange(daysInPast=70,includeAllActive=false)

响应

以下示例显示了相应的响应。

注意:为了提高可读性,可能缩短了此处显示的响应对象。

HTTP/1.1 200 OK
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/beta/$metadata#Collection(microsoft.graph.windowsUpdates.knownIssue)",
  "value": [
    {
      "id": "WI670072",
      "status": "mitigatedExternal",
      "webViewUrl": "https://admin.microsoft.com/Adminportal/Home#/windowsreleasehealth/knownissues/:/issue/WI670072",
      "description": "Investigation concluded that the error reported by users was not caused by the August 2023 preview updates.",
      "startDateTime": "2023-08-22T10:00:00-07:00",
      "title": "Microsoft received reports about an “UNSUPPORTED_PROCESSOR” error",
      "resolvedDateTime": "2023-09-07T16:14:07.1881817-07:00",
      "lastUpdatedDateTime": "2023-09-07T16:41:58.577-07:00",
      "originatingKnowledgeBaseArticle": {
        "Url": "https://support.microsoft.com/help/5029351",
        "Id": "KB5029351"
      },
      "resolvingKnowledgeBaseArticle": null,
      "safeguardHoldIds": [],
      "knownIssueHistories": [
        {
          "createdDateTime": "2023-08-24T02:51:27.29Z",
          "body": {
            "content": "Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 (KB5029351 (https://support.microsoft.com/help/5029351)) and then restarting their device. KB5029351 (https://support.microsoft.com/help/5029351) might automatically uninstall to allow Windows to start up as expected. KB5029351 (https://support.microsoft.com/help/5029351) might not offer to some Windows devices which might be affected by this issue.\n\nIf you are experiencing issues, please use Feedback Hub to file a report following the below steps:\n    1. Launch Feedback Hub by opening the Start menu and typing \"Feedback hub\", or pressing the Windows key + F\n    2. Fill in the \"Summarize your feedback\" and \"Explain in more detail\" boxes, then click Next.\n    3. Under the \"Choose a category\" section, click the \"Problem\" button, and select \"Install and Update\" category. Then select \"Downloading, installing, and configuring Windows Update” subcategory. Click Next.\n    4. Under the \"Find similar feedback\" section, select the \"Make new bug\" radio button and click Next.\n    5. Under the \"Add more details\" section, supply any relevant detail (Note this is not critical to addressing your issue).\n    6. Expand the \"Recreate my problem\" box and press \"Start recording\". Reproduce the issue on your device.\n    7. Press \"Stop recording\" once finished. Click the \"Submit\" button.\nFor additional information, see Send feedback to Microsoft with the Feedback Hub app (https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332).\n\nNext steps: We are presently investigating to determine if this is an issue caused by Microsoft. We will provide an update when more information is available.\n\nAffected platforms:\n    -  Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2\n    -  Server: None\n",
            "contentType": "html"
          }
        }
      ]
    }
  ]
}