Solving a common problem

Use the exact symptom below and perform the checks in order. Before repairing a file or replacing a value, make a copy of the relevant .mywealth file.

“The file cannot be opened”

Check the file's full name and .mywealth extension.
Copy the synchronised or received file to a local folder, then open the copy.
For an encrypted file, check Caps Lock and the keyboard layout before entering the password again.
On Windows, find the .bak files beside the document. Copy one and rename the copy with the .mywealth extension.
On Android, select the document again in the picker if the permission granted to the provider has expired.

An opening error does not replace the wealth file that is already open.

“Saving failed”

On Windows, try Save as in a local folder where you can create a file. If this succeeds, the problem probably comes from the previous destination. On Android, check the document provider, then choose a new permanent location. Do not overwrite the old copy until you have reopened the new one.

“Partial result” or “Exchange rate required”

Note the two currencies and their direction in the message.
Use Enter rate or open Properties > Exchange rates.
Replace the 0 rate with the value of one unit of the source currency in the target currency.
Apply, then return to the view.

If the total remains partial, a second pair may be missing. A Live update may also complete available conversions.

An asset is not updated by Live

Open the asset and check that it has a Live identifier matching the correct market and currency. Run Refresh prices again and read the final summary. An asset created manually without a compatible source must be valued manually; its existing value is not replaced with zero if an update fails.

The local AI assistant does not start

Under Settings > Local AI, check that an installed model is selected.
Under Properties > Artificial intelligence, enable viewing for this wealth file.
Close applications that use a lot of memory.
In the model settings, try CPU only to distinguish a graphics issue from a model issue.
If the small model works, select a less demanding profile or use Determine automatically in custom mode.

A CPU fallback can make the first start considerably slower without being a failure.

An MCP application cannot see the wealth file

Check that the server reports Running, a wealth file is open, and Allow viewing via MCP is enabled in its properties. If you replaced the token, copy the new configuration into the client application.

“My wealth appears to be counted twice”

A support has no value of its own: it organises items and can carry their ownership. Instead, look for an asset created twice, an account present in two families, or a quantity and total value entered instead of a quantity and unit price. A current account, savings account, or property should be created only once as an asset.

“The Android file does not contain my latest change”

Check that saving has finished on the first device and that your file provider has completed synchronisation. Do not edit the same wealth file simultaneously on Windows and Android. If a “conflicted” file was created, keep both versions until you have identified the newest one.

“My net wealth does not match the expected result”

Check the value and currency of assets, the outstanding principal of liabilities, and the required exchange rates. A liability represents the outstanding principal and must not replace the value of the financed property.

Reporting the problem

From help or settings, use the available report action. State the version, Windows or Android, the exact action, the full message text, and whether the problem recurs with a copy of the file.

Attach the wealth file only after checking its contents and only if you explicitly agree to transmit this data. For an AI or MCP problem, attach the diagnostic logs offered by the application instead.