I've tried the methods but they still don't work. I don't know what to do.

The update notes you found address File History access to network shares; they do not promise a repair for local-drive history or create missing versions. Because the target is D: and new files show “No previous versions,” first confirm File History is enabled and D: remains the selected drive. Then use “Restore personal files” to look for an older copy of a file changed before the issue; versions exist only after a successful history run captured them. Check the File History event log for errors when a backup should run, confirm D: is connected with its normal letter, and verify available space. Avoid deleting the configuration until you copy any history elsewhere, because a new configuration can establish a new baseline. If the log shows repeated failures, record the event IDs and Windows build before escalating. The SMB release-note fix is not evidence that it resolves this local-drive symptom.