Ah, ok, you're right.@AHeyne
...I'm using a different OS for that VM so I don't think it would prove anything
Well, it seems the super moderator does not this thread to continue. I cannot flag this as "solved". So, I will flag this as "unwatched" and respond to anymore posts.
For those of you, that tried to help, I am grateful.
Going offline now/
IIRC, many AV applications, like Norton or McAfee. have "white list" or "black list" options for various programs, which usually means Access needs to called out in those cases.Probably that means that McAfee had downgraded its "opinion" of Access, which in turn probably means it could have been fixed by going into McAfee to make Access fully trusted. Since I don't have McAfee I don't know the exact method to tell it to trust a particular program, but I had a similar problem for a different utility program with Kaspersky and changing its trust level was my solution. DIdn't think of that in your context, I guess because the AV package didn't come up in the thread. Glad you found out - and thanks for publishing your answer. Others who search for DB startup-display problems might learn something very useful.
OP posted 11 more times there before disabling AV. So yeah to post 126 here.Found another possibility - AV. Perhaps the "good" pc has none, or a different version, or a different setting. I don't know (or forgot) what environment you're working in, so AV might not apply. AV should not be scanning mdb files if that is the case.