> 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/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/readme/nin-ke-yi-an-zhuang-na-xie-ban-ben-de-windows.md).

# 您可以安裝哪些版本的 Windows

Parallels Desktop for Mac 27 支援安裝專為在 Arm 處理器上運行而設計的 Windows 11 Pro 及 Enterprise 版本。本版本起，已不再支援 Intel 架構的 Mac 電腦。

近年來銷售的大多數 Mac 電腦均採用 Apple Silicon 處理器，並獲得 Parallels Desktop 27 的全面支援。

雖然有些 Windows 應用程式是專為 Intel (x86/x64) Windows 個人電腦設計的，但微軟的 Prism 相容性技術讓其中許多應用程式能夠在基於 Arm 的系統上運行，包括虛擬機器。 這意味著大多數常見的生產力、商務及開發者應用程式，皆可在 Parallels Desktop 27 中的 Windows 11 虛擬機器上運行。然而，少數特殊應用程式（尤其是那些依賴硬體驅動程式、低階系統元件或特定反作弊技術的應用程式）可能無法相容。

Parallels 會定期測試熱門的 Windows 應用程式，以確保其與我們最新軟體的相容性，並致力於提供最佳的效能。

{% hint style="info" %}
**注意**：儘管已不再支援 Intel Mac，但 Parallels Desktop 27 的 Pro、Business 和 Enterprise 版本仍可在 Apple Silicon Mac 上匯入並執行 x86\_64 虛擬機器。 此功能目前處於早期技術預覽階段，主要適用於系統遷移與測試情境。由於 x86\_64 作業系統必須完全透過模擬運作，其效能將遠低於原生 Arm 虛擬機器，且部分功能可能無法使用或不受支援。

您可以在本指南的「進階主題」章節中找到更多相關資訊。
{% endhint %}

本指南主要著重於如何使用 Parallels Desktop 執行 Windows 11，並在適當時提及其他作業系統。


---

# 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/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/readme/nin-ke-yi-an-zhuang-na-xie-ban-ben-de-windows.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.