> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/references/database-information-and-organization/metro-apps.md).

# Metro apps

Windows Metro apps behave differently from normal Windows applications. The Nexthink solution abstracts those differences in order to provide a comprehensive view of the user activity.

### Executions of metro apps <a href="#metroapps-executionsofmetroapps" id="metroapps-executionsofmetroapps"></a>

There are mainly two kinds of architectures for metro apps: compiled and JavaScript. Compiled applications (written in C#, VisualBasic or C++) behave similarly to normal Windows applications and have a `.exe` file associated with them. JavaScript applications are not compiled and there is no associated `.exe` file. Instead, the default windows executable hosts `WWAHost.exe` them. When analyzing the task manager of Windows devices, we usually see several executions of WWAHost, each one corresponding to a specific metro app.

Reporting only executions of WWAHost does not allow Nexthink users to distinguish between different metro apps. Instead, Nexthink Collector abstracts this information and reconstructs names and properties of the metro app being hosted by WWAHost by reporting this as a binary. The system uses similar techniques to abstract the corresponding executables and applications.

The system reports executions, connections, web requests, crashes, freezes, and other, routinely. The Nexthink solution makes it possible to distinguish between the web requests performed by the *Weather* app and the *Food & Drink* app. The description field of Metro executables is always set to *Windows Metro Style App*.

### Metro packages <a href="#metroapps-metropackages" id="metroapps-metropackages"></a>

Metro apps are also different from a packaging perspective. You do not install them not like traditional applications and are not visible in Windows **Programs and Features**. As for binaries, Nexthink abstracts these differences: the system reports all metro apps as a **Package** and also reports the corresponding installations and uninstallations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/references/database-information-and-organization/metro-apps.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.