• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Microsoft Store install dates

Shrek

Shrek

Joined
Mar 21, 2021
Messages
4,578 (3.90/day)
Location
Colorado, U.S.A.
System Specs
System Name CyberPowerPC ET8070
Processor Intel Core i5-10400F
Motherboard Gigabyte B460M DS3H AC-Y1
Memory 2 x Crucial Ballistix 8GB DDR4-3000
Video Card(s) MSI Nvidia GeForce GTX 1660 Super
Storage 500GB SN550 WD Blue NVMe M.2
Display(s) Dell P2416D (2560 x 1440)
Power Supply Apevia 600W Gold 80 Plus
Software Windows 11 Home
Just got this installation date on the Microsoft Store: 1/1/0001

It has now fixed itself to "Modified minutes ago"

maybe it is always like this


111.JPG
 
cvaldes

cvaldes

Joined
Jun 21, 2021
Messages
2,910 (2.69/day)
System Specs
System Name daily driver Mac mini M2 Pro
Processor Apple proprietary M2 Pro (6 p-cores, 4 e-cores)
Motherboard Apple proprietary
Cooling Apple proprietary
Memory Apple proprietary 16GB LPDDR5 unified memory
Video Card(s) Apple proprietary M2 Pro (16-core GPU)
Storage Apple proprietary onboard 512GB SSD + various external HDDs
Display(s) LG 27UL850W (4K@60Hz IPS)
Case Apple proprietary
Audio Device(s) Apple proprietary
Power Supply Apple proprietary
Mouse Apple Magic Trackpad 2
Keyboard Keychron K1 tenkeyless (Gateron Reds)
Software macOS Ventura 13.6 (with latest patches)
Benchmark Scores (My Windows daily driver is a Beelink Mini S12 Pro. I'm not interested in benchmarking.)
Yeah, I get these nonsensical install dates for several software packages on multiple Windows systems.

Since it's Microsloth, I just shrug it off to basic incompetence and carry on.

You can worry about it but don't expect an enlightening explanation here at TPU. I know it is very fashionable to slander Apple at every opportunity here but I haven't seen this type of error in multiple decades running Macs. Translation: the Mac App Store isn't the steaming heap of dung that the Microsoft App Store is.

And while Microsoft is cleaning up App Store dates, maybe they can do something about inscrutable hexadecimal error codes on Windows Update. But I won't hold my breath on that... Ahaha

Best of luck.
 
Last edited:
Shihab

Shihab

Joined
Jan 10, 2011
Messages
1,347 (0.28/day)
Location
[Formerly] Khartoum, Sudan.
System Specs
System Name 192.168.1.1~192.168.1.100
Processor AMD Ryzen5 5600G.
Motherboard Gigabyte B550m DS3H.
Cooling AMD Wraith Stealth.
Memory 16GB Crucial DDR4.
Video Card(s) Gigabyte GTX 1080 OC (Underclocked, underpowered).
Storage Samsung 980 NVME 500GB && Assortment of SSDs.
Display(s) LG 24MK430 primary && Samsung S24D590 secondary
Case Corsair Graphite 780T.
Audio Device(s) On-Board.
Power Supply SeaSonic CORE GM-650.
Mouse Coolermaster MM530.
Keyboard Kingston HyperX Alloy FPS.
VR HMD A pair of OP spectacles.
Software Ubuntu 22.04 LTS.
Benchmark Scores Me no know English. What bench mean? Bench like one sit on?
01/01/0001 is equivalent to the earliest date .NET supports. See:
learn.microsoft.com

DateTime.MinValue Field (System)

Represents the smallest possible value of DateTime. This field is read-only.
learn.microsoft.com

Given that the displayed value changed to a text, I'm guessing the program has an unnecessarily complicated routine for displaying the date (instead of just retrieving the fixed date from log) for recently installed/updated applications. A routine which is obviously bugged in a way that returns MinValue as you see.

Unless it's causing errors running the application or updating or uninstalling it, I don't think it's something to worry about. Just write it off as lack of proper QA as is the case with post-Windows 10 Microsoft.
 
You must log in or register to reply here.
Top