OS Install Date: Dec 31 1969

[SoberDoper®]

why does my SYSTEM INFORMATION found in HELP on the bar show that my o/s is from 1969 or that GAME CONTROLLERS; NONE DETECTED is wrong as I have , up to last Mondays update, a joystick that I was using.

[d7602002]

I was on another thread and some one had the same exact thing. It was weird...

it is steam not reading it properly. I found through a google search that it happens a lot more than you think, but with 1 caveat...some people are dec 31 1969 while others are Jan 1, 1970...depends on what side of the Univeral Time ((UTC) you are on.

[Silicon Vampire]

After reading this more carefully and looking at my own system info, I regret moving this thread here and will move it back as soon as I can.

At first I thought it would be a clock not set properly when installing the OS but realized when I looked at mine it reported the same thing and I know my clock was set properly when I installed W7.

EDIT -----------------------

Moved back.

[SirEpicFail]

I noticed that months ago and was wondering that too.

[PC]

i have win7 64 bit but it shows that i have win vista 64 bit?

[Junipercat]

This still happens with Steam Survey as of today

[Washell]

Messaggio originale di Junipercat:

This still happens with Steam Survey as of today

Because it's an unfixable issue.

The installation date is stored as a unix timestamp, which is an integer counting the seconds from 00:00:00 January 1st 1970. At time of this post, it's 1517609837 seconds past 00:00:00 January 1st 1970.

-1 is often used to indicate no data, which translates to a second before 00:00 January 1st 1970, which turns out to be 23:59:59 December 31st, 1969.

Alternatively 0 or NULL are used, which is 00:00:00 January 1st 1970.

There's nothing Valve can do to fix this.

[Me262Schwalbe1]

is it possible it mean our Os windows 7/8/10 was based on Unix and Dos ???for it's function in terms of write code and zero's and one's?

[DrawingBoard]

Still happening in 2020.

[Iceira]

Battery on mortherboard can get broken and that mean it reset or cant keep cmos, and i doubt anyone here has a pc from past 2000 bug. ( google mortherboard and ask support there. )

[Zekiran]

OEM systems do that, and will always do that, and it's not a broken anything. It's because UNIX is unable to parse certain information.

This is working as intended and not a bug that can be fixed.