could not compile winit due to 3 previous errors

[Sanookmakmak]

I have changed the Cargo.toml file to

[package]
edition = "2021"

after running

cargo build --release

only a few errors occur:

error[E0432]: unresolved import `winapi::shared::winerror`
  --> C:\Users\XX\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.16.2\src\platform\windows\dpi.rs:15:21
   |
15 | use winapi::shared::winerror::S_OK;
   |                     ^^^^^^^^ could not find `winerror` in `shared`

error[E0432]: unresolved import `winapi::um::errhandlingapi`
 --> C:\Users\XX\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.16.2\src\platform\windows\util.rs:7:17
  |
7 | use winapi::um::errhandlingapi::GetLastError;
  |                 ^^^^^^^^^^^^^^ could not find `errhandlingapi` in `um`

error[E0432]: unresolved import `winapi::shared::winerror`
    --> C:\Users\XX\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.16.2\src\platform\windows\window.rs:1153:33
     |
1153 |             use winapi::shared::winerror::S_OK;
     |                                 ^^^^^^^^ could not find `winerror` in `shared`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `winit` due to 3 previous errors
warning: build failed, waiting for other jobs to finish...

Output of

rustc --explain E0432

An import was unresolved.

Erroneous code example:

use something::Foo; // error: unresolved import `something::Foo`.

In Rust 2015, paths in `use` statements are relative to the crate root. To
import items relative to the current and parent modules, use the `self::` and
`super::` prefixes, respectively.

In Rust 2018 or later, paths in `use` statements are relative to the current
module unless they begin with the name of a crate or a literal `crate::`, in
which case they start from the crate root. As in Rust 2015 code, the `self::`
and `super::` prefixes refer to the current and parent modules respectively.

Also verify that you didn't misspell the import name and that the import exists
in the module from where you tried to import it. Example:

use self::something::Foo; // Ok.

mod something {
    pub struct Foo;
}

If you tried to use a module from an external crate and are using Rust 2015,
you may have missed the `extern crate` declaration (which is usually placed in
the crate root):

extern crate core; // Required to use the `core` crate in Rust 2015.

use core::any;

Since Rust 2018 the `extern crate` declaration is not required and
you can instead just `use` it:

use core::any; // No extern crate required in Rust 2018.