Windows 10: Stuck at Verifying Usn Journal...

My computer, when booting windows 7 runs chk dsk. When it's almost complete it stops at verifying Usn journal...What can I do to make the system go past that point?

:)

 

"CHKDSK is resetting USN information..." message stuck at 2%, what?

I did the disk check today (May 3) after a couple of attempts doing the CHKDSK thing.

I did the disk check right now using command prompt without doing the next reboot and I started it at 1:12 PM with no issues. But after at about 3:00 PM it says this:

"34986 data files processed.

CHKDSK is verifying Usn Journal...

Repairing Usn Journal $J data stream.

CHKDSK is resetting Usn information...

2 percent completed."

I have no idea what to do right now, should I stop the disk check? Will it delete all of its data? Or is it normal?

Please tell me what to do with this, I tried searching with this message "CHKDSK is resetting Usn information..." and... No results.

Now I'm running for like 2 1/2 hours (2 and a half hours) and no changes. Please help me!

Best regards,

Wai Min Soe

 

Repair SBS 2011 from USN Journal Rollback issue after recovery

Hi,

I was unfortunately forced to use Veeam B&R with NON-Application Aware backup to roll-back entire SBS 2011 server to restore functionality. This brought SBS 2011 into USN Journal Rollback state 0x4, so now I have the following situation:

• SBS 2011 with Exchange into USB Rollback 0x4 state, with NETLOGON service Paused
• and 2 additional DCs in the same domain. Those replicate between each other just fine

Maybe important thing is, that since that happened (yesterday), there has been actually
NO SIGNIFICANT CHANGES to AD objects made since we did rollback. No passwords changed, no GPOs changed, no new users....

I've gone through quite some tech articles, and they suggest DEMOTING problematic DC from domain, which I think in my case is not an option (it's SBS with Exchange...probably will broke). Secondly, they suggest restoring only System State...but unfortunately
no other backup is healthy, only Veeam with non-app-aware state.

But one article suggested this:

1. Check for USN rollback by using the command Repadmin /showutdvec (KB Article: 875495, 885875)

2. Check the Registry value "HKLM\System\CurrentControlSet\Services\NTDS\Parameters, "DSA Not Writable" (REG_DWORD) and its value is
0x4.

Both (1) and (2) are confirmed, state in REG is 0x4, and NETLOGON service paused

3. Delete "DSA Not Writable" (REG_DWORD) from registry and reboot the server.

Hmmm...this looks logical to me. What do you think? Is this my easy solution?

Thoughts?

 

Old Windows Journal

Hi,

It is possible that Windows Journal was removed from certain versions of the Windows operating system due to corrupted system files. To provide you the accurate resolution, we'd like to gather more information:

• Have you made any recent changes prior to this issue?
• Are you getting any error messages?
• Which build and version of Windows 10 are you using?
• What troubleshooting steps have you done so far?

Meanwhile, we suggest that you follow the steps in article on how you can install Windows Journal on
versions of Windows from which it was removed.

Keep us posted if you need additional help.