Windows 10: Read-only USB and ESENT error

I have a problem I don't know how to solve.


- I have a USB with an "only-read" state (no viruses, probably from taking it out without the proper measures).

- I have tried multiples times to clear the read-only problem to be able to format the USB. I have tried using "DiskPart.exe", selecting the unit I am having problems with and executing "attribute disk clear readonly".

- When I try to execute "clean" or to make sure it is not "read-only" anymore, "diskpart.exe" says "their have been an error...check the system's Event Viewer to obtain more information".

- I then find out that the problem is source: ESENT, ID: 455.


From here, I have no idea how to solve the problem. How do I get my USB unit to not be read-only so I can format it? And also, how do I solve the ESENT that keeps happening?


Thank you very much,

Kiwi

:)

 

Undocumented ESENT error code 0x800000 WON'T SHUT UP

The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000

My computer makes a noise every 3 or 4 minutes. The event viewer shows this message. I found a list of ESENT error codes elsewhere on this site. That one is not on the list.

There are no circumstances under which Windows should issue an error sound without a dialog box explaining what the sound is for, nor issue an error code that is undocumented. I'm tempted to just turn off that sound but then I might miss something actually
important.

 

ESENT 916

Thank you for the updates. Can you give me the full details of the error using the Event Viewer? When the error happens or shows, do these steps:

1. Press Windows key on your keyboard, type Event Viewer and select the search result.
2. On the left hand pane, click Windows Logs, and select
   Application.
3. On the Source column, there should be an ESENT
   with an Event ID of 916. Click the item and on the bottom pane, copy the information on the General tab and paste it here.

For now, according to my research, this may be closely related to hard drives. Can you give me information on what is the make and model of your hard drive?

I'll be waiting for your reply.

 

Error ESENT Event ID 413 Logging/Recovery

I was getting over 50 ESENT errors in the event viewer after each reboot. I tried SFC /SCANNOW, DISM, CHKDSK /R. It did not work.........................

I then created a new profile, rebooted and logged in with the new profile. The ESENT errors are now gone. The system runs smooth. Many other errors that event viewer was listing are also gone now.
The old profile was corrupt. The new profile works great!!!!!!!!!!!!!!!!