Unable to link Windows Kernel32 library native methods and handlers will be disabled – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to access the Kernel32 library, a critical component of the Windows operating system. This could be due to incorrect permissions, missing files, or an incompatible version of the library. To resolve this issue, you can try reinstalling or updating your operating system to ensure the Kernel32 library is present and accessible. Alternatively, you can run Elasticsearch with administrator privileges to ensure it has the necessary permissions. Lastly, ensure that your version of Elasticsearch is compatible with your version of Windows.

We recommend you run Elasticsearch Error Check-Up that will review your configuration and resolve issues that cause many errors.

This guide will explain what causes the log “deleting index” to appear and how to resolve this.


To learn about indices in Elasticsearch, read this guide: Elasticsearch Index.

What does this message mean?

When you use the DELETE API, you’ll see the following logs:

[2022-02-12T13:15:46,541][INFO ][o.e.c.m.MetadataDeleteIndexService] [opster] [my_index/gnQA70A1TVWFns7Yp2728Q] deleting index

This is an INFO message informing you that the index `my_index` is being removed from the node.

It’s very important to know that If you don’t have a snapshot or backup set up, you won’t be able to recover the index once it’s been removed.

How to reproduce this log

Make sure your Elasticsearch instance is running before proceeding with the following steps.

Create index:

Using the PUT API, create an index (let’s call it `my_index`):

PUT /my_index

Delete index:

The next step is to use the DELETE API to delete the index:

DELETE /my_index

Log Context

Log “unable to link Windows/Kernel32 library. native methods and handlers will be disabled.” classname is JNAKernel32Library.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                logger.debug("windows/Kernel32 library loaded");
            } catch (NoClassDefFoundError e) {
                logger.warn("JNA not found. native methods and handlers will be disabled.");
            } catch (UnsatisfiedLinkError e) {
                logger.warn("unable to link Windows/Kernel32 library. native methods and handlers will be disabled.");

    static JNAKernel32Library getInstance() {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?