# Page Not Found

The URL `isletim-sistemleri/windows-11/windows-11-microsoft-store-uezerinden-wsl-kurulumu` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Windows Mağazasından yüklenen uygulamaların kısayolunu oluşturma](https://herrwinfried.gitbook.io/tr/os/windows-11/windows-magazasindan-yuklenen-uygulamalarin-kisayolunu-olusturma.md)
- [Hyper-v açık olmasına rağmen çalışmıyor](https://herrwinfried.gitbook.io/tr/os/windows-11/hyper-v-acik-olmasina-ragmen-calismiyor.md)
- [winget kullanımı](https://herrwinfried.gitbook.io/tr/os/windows-11/winget-kullanimi.md)
- [Hyper-V ve Hyper-V yöneticisi aktif etme](https://herrwinfried.gitbook.io/tr/os/windows-11/hyper-v-ve-hyper-v-yoneticisi-aktif-etme.md)
- [Windows 11](https://herrwinfried.gitbook.io/tr/os/windows-11.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

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

```
GET https://herrwinfried.gitbook.io/tr/os/windows-11/windows-magazasindan-yuklenen-uygulamalarin-kisayolunu-olusturma.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 `build a script that syncs our docs to a CMS` 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.

### Option 2 — Browse the documentation index

Full index: https://herrwinfried.gitbook.io/tr/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://herrwinfried.gitbook.io/tr/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/tr/os/windows-11/windows-magazasindan-yuklenen-uygulamalarin-kisayolunu-olusturma.md`).

You may also use `Accept: text/markdown` header for content negotiation.