Y2K38. 32bit Windows defeated

Topic

New Reply

https://twitter.com/endermanch/status/1765072579541537074

“Setting year 2038 on 32-bit versions of Windows (incl. Windows 10) breaks some core functionality, as shown in the video.

A great reminder for you all to make sure you’re running a 64-bit version of Windows.”

https://www.neowin.net/news/remember-y2k-windows-95-98-2000-era-app-surprisingly-stands-tall-against-y2k38-superbug/

Unix time, also known as POSIX (Portable Operating System Interface) time, is a measurement of time that counts the number of seconds that have passed since January 1, 1970. This date is referred to as the Unix Epoch, and hence the term “Epochalypse.” Under such operating systems, date values are stored in a signed 32-bit integer indicating the number of seconds since January 1, 1970. A problem arises with the 32-bit integer overflowing at approximately 0314 hours on January 19, 2038, causing systems to interpret the date value as December 13, 1901.

2 users thanked author for this post.

JPMedia, Cybertooth

Reply | Quote

Replies

well nobody should be running a 32bit version of windows when year 2038 actually arrives as all 32bit OSes (whether Windows, macOS, Linux or android) are already EOL

Reply | Quote

Regardless of our personal opinions on the matter, there are guaranteed to still be people out there running 32 bit operating systems, such as Windows XP, on native hardware through 2038. It’s better to have the ability to keep those systems running than not.

1 user thanked author for this post.

Alex5723

Reply | Quote