after automatic update jenkins fails with `InvalidBuildsDir: .../${ITEM_FULL_NAME}/builds does not resolve to an absolute path`
I'm not very familiar with Jenkins on Windows, but I imagine your issue lies in the fact installing Jenkins on drives other than C:\ are more difficult to deal with. Since Jenkins is not running, you'll have to configure config.xml by hand.
Here's a post on stackoverflow.com that may help you. As they state, you'll probably need to find the Workspace Root Directory to D:\Jenkins\${ITEM_FULL_NAME}\workspace and Build Record Root Directory to D:\Jenkins\${ITEM_FULL_NAME}\builds (or whatever values are specific to your environment) in your config.xml.
The post also mentions the bubble help info that is useful:

This value may include the following variables:

${JENKINS_HOME} — Absolute path of the Jenkins home directory

${ITEM_ROOTDIR} — Absolute path of the directory where Jenkins stores the configuration and related metadata for a given job

${ITEM_FULL_NAME} — The full name of a given job, which may be slash-separated, e.g. foo/bar for the job bar in folder foo


The value should normally include ${ITEM_ROOTDIR} or ${ITEM_FULL_NAME}, otherwise different jobs will end up sharing the same workspace.