> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/release-notes/8_2sp1.md).

# IDA 8.2sp1

**IDA 8.2.230124 (SP1)** ***January 24, 2023***

This Service Pack of IDA 8.2 is primarily a bugfix release.

#### Improvements:

* \+ RISCV: added all currently ratified extensions (cryptography, wait on reservation, pause, cache managment, state enable, hypervisor etc.)
* \+ RISCV: improve handling of lui + auipc or addi pairs
* \+ UI: allow the user to specify a not currently available Lumina server
* \+ UI: make the caret (cursor) color configurable

#### Bugfixes

* BUGFIX: decompiler: changing variable types could cause the decompiler to crash
* BUGFIX: eh\_parse: x64 PE binaries compiled with recent llvm-based compilers (15.x) could have numerous off-by-one disassembly errors
* BUGFIX: fixed internal error 1112 which could occur when disassembling some Motorola 68K instructions
* BUGFIX: IDAPython: added workaround for Python 3.11.1 on Windows failing to import ctypes and other standard native modules
* BUGFIX: IDAPython: PyQt5 was not working with Python 3.11
* BUGFIX: IDAPython: upon failure, `ida_hexrays.decompile()` now always returns `None` instead of either throwing a `ida_hexrays.DecompilationFailure` or returning `None`.
* BUGFIX: RISCV : fixed decoding of floating-point conversion and comparison instructions
* BUGFIX: ui/qt: "List cross-references to..." would not be in the context menu anymore even when some Xrefs are codesent
* BUGFIX: ui/qt: some informational wait dialogs wouldn't show anymore

[See all releases](/release-notes.md)


---

# 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.hex-rays.com/release-notes/8_2sp1.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.