> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos/jiang-windows-she-wei-chu-xian-zai-dan-yi-shi-chuang.md).

# 將 Windows 設為出現在單一視窗

您可以將 Windows 和其應用程式設定為一起出現在其自己的視窗中。

<figure><img src="https://content.gitbook.com/content/NPLQPyrTCZG7rj2GnqwJ/blobs/tEozBOj86L80395S38zO/image.png" alt="" width="563"><figcaption><p>Windows 11 in a Single Window Mode</p></figcaption></figure>

{% hint style="info" %}
**附註**：Parallels Desktop App Store Edition 不支援融合模式。如需 Standard Edition 和 App Store Edition 差異的詳細資訊，請前往此[連結](https://kb.parallels.com/123796)。
{% endhint %}

選擇以下其中一種方法從融合 (Coherence) 模式切換為視窗模式：

* 按一下功能表列中的 Parallels Desktop 圖示，然後選擇「**查看**」>「**退出融合 (Coherence)**」。
* 如果 Parallels Desktop 功能表出現在 Mac 功能表，請按一下「**檢視**」>「**退出融合 (Coherence)**」模式。

選擇以下其中一種方法從全螢幕模式切換為視窗模式：

* 按下 Command-Control-F。
* 移動指標到螢幕頂部直到 macOS 功能表列出現，並按一下「**檢視**」>「**結束全螢幕**」。如果您使用針對遊戲最佳化的「全螢幕」，按下 Control-Option (Alt) 以顯示 Mac 功能表列。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pdfm-ug/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos/jiang-windows-she-wei-chu-xian-zai-dan-yi-shi-chuang.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.