How to find out the date Windows 11 or an app was installed

Many times we wonder How old is our computer in reality, or how long has Windows 11 been installed?Especially when it starts running slower than usual or we're considering formatting. It's also common to want to know when we install a specific program or appFor example, an antivirus like Avast, to find out if it came pre-installed or if we installed it ourselves at some point and we don't even remember.

The problem is that, if we simply look at the list of “Applications” in Windows settings, the dates that appear usually correspond to the last app update and not the original installation. This makes it easy to get confused, especially with pre-installed programs or those that are frequently updated. Luckily, Windows stores quite a bit of internal information, and with a few tricks, we can find out. when Windows 11 was installed, when the PC was roughly assembled, and in some cases, the actual age of certain apps.

Why is it useful to know when Windows 11 or an app was installed?

Beyond simple curiosity, getting to know the Windows 11 installation date And the approximate "age" of the equipment can help you make practical decisions. For example, it can help you assess whether it's time for an upgrade. clean system installation, whether your second-hand PC is older than they told you or whether it's worth investing in a hardware upgrade.

It is also very common to want to check Since when has an antivirus or other security program been installed?In cases like Avast One, many people wonder if it came pre-installed with Windows or if they installed it at some point and no longer remember. There's an important distinction here: Windows doesn't directly and reliably display the date an application was first used, and in many cases, we can only... infer a reasonable estimate from other system data.

It should also be noted that Windows treats the major system updatesIn Windows 10 (and, to some extent, in Windows 11 as well), certain "mega-updates" are registered as if they were practically a fresh installation, with their own date in the Registry. This means that what you see as the "original installation date" may actually be the day you upgraded to a major version of the system.

Therefore, instead of relying on just one isolated piece of data, it is advisable to combine several sources: BIOS/UEFI date, CPU model and release year, Windows installation date, and, if necessary, disk and app dataWith this set of information, a fairly reliable picture of the PC's life and its software can be drawn.

Check the age of the PC by the BIOS or UEFI date

A very simple way to approximate the "age" of the computer is to look at the BIOS or UEFI dateIt's not perfect data, but it usually indicates when the motherboard left the factory or when it received its first firmware, which gives us a fairly clear timeframe for the assembly of the equipment.

To view this information without physically accessing the BIOS, Windows provides a built-in tool: System informationAccessing it is very easy and you don't need to be an expert; just use a quick command and locate the correct field.

In Windows 11, you can open the “Run” dialog box by pressing Windows + R on the keyboard. In the window that opens, type msinfo32 and press Enter. This will launch the System Information utility, which displays a very detailed summary of the installed hardware and software.

Within that window, in the main panel, you'll see many fields: system name, BIOS version, manufacturer, etc. The one we're interested in for this section is the BIOS date or “BIOS Date/Version”. This date is usually very close to when the motherboard was manufactured or received its first working firmware version.

If the date shown is more recent than the day you bought the device, it may be because at some point it was updated the BIOS or UEFIIn that case, the date you see corresponds to that newer firmware, not the original. Even so, combining that information with other data will help you narrow down the time range of your PC.

Identify the CPU and find its release year

Another key element in placing your team in time is knowing What processor (CPU) does it have and in what year was it released?The computer cannot be older than the release of that CPU model, so with that information you will establish a fairly reliable timeframe.

To see the exact model of your processor in Windows 11, the easiest way is to open the Task ManagerYou can do it quickly by pressing the combination Ctrl + Shift + Esc or by right-clicking on the taskbar and choosing “Task Manager”.

Once inside, go to the tab "Performance" and select “CPU” in the left-hand column. In the upper right corner of the CPU usage graph, you’ll see the full processor name: for example, something like “Intel Core i5-10400F” or “AMD Ryzen 5 5600X.” It’s important that copy that name exactlybecause a simple number up or down already indicates a different model.

With the model outlined, the next step is to enter the official website of the manufacturer to check the release year. In the case of Intel, the reference is Intel ARK, their processor database, where you can search for the model and see the release date. If your CPU is AMD, you'll need to go to the official AMD processor specifications, where the moment when that family of chips was made public is also indicated.

That release year marks the earliest time your PC could have been assembled. For example, if your BIOS is dated 2019 and your CPU was released in 2020, it's clear the system assembly had to have been done after that date. Hereinafter 2020These aren't Windows installation dates per se, but they do give you valuable context about the overall age of the hardware.

View the Windows installation date using PowerShell

If what you want to know is When exactly was Windows 11 installed on your computer?One of the most direct and convenient ways is to use PowerShellIt's the modern Windows console, more powerful than the classic command prompt, and allows access to system information with a simple command or with installation scripts.

To open PowerShell in Windows 11, you can use the Start menu search bar, type "PowerShell," and run it with normal user privileges. There's no need to run it as administrator just to check the installation date. Once open, you'll see the familiar blue or black window where you can enter commands.

The cmdlet we're interested in is very short. Just type the following and press Enter: (Get-CimInstance -Class Win32_OperatingSystem).InstallDatePowerShell will query the operating system class and return the value of its “InstallDate” property, which corresponds to the Date on which the current version of Windows was installed on that device.

The output may be displayed in a readable date format or include more technical information depending on your regional settings, but essentially it will tell you the day your system was installed (or reinstalled). If that date is very recent and doesn't coincide at all with when you bought your PC, it's likely that you recently reinstalled Windows or that a major update has been applied which, from the system's perspective, counts almost as a new installation.

On the other hand, if the date is very similar to when you first got the equipment, that reinforces the idea that You're still using the same base Windows installation since then, which can be a useful clue to assess whether it's time for a deep "reset" to lighten the system.

Get the Windows installation date using systeminfo

If you don't want to use PowerShell or you're working in an environment where it's not available, you can use the classic command systeminfowhich works from the command prompt (CMD) and also provides the original Windows installation date.

To use it, open the command prompt by searching for “cmd” in the Start menu and running “Command Prompt”. In the window that opens, simply type systeminfo and press Enter. Windows will collect a large amount of data about the system: hostname, OS version, build type, installed memory, network, etc.

Among all that information, you'll see a field called something very similar to “Original installation date”where the exact date the operating system was installed is indicated. This information is equivalent to what we obtain with PowerShell, but presented in a more "traditional" way.

To avoid having to manually review the entire list, it's very practical to filter the command's output and keep only the line we're interested in. On Spanish-language systems, you can use: systeminfo | find /i «original»Thus, the command prompt will only display the line containing that word, where the original Windows installation date appears.

If your Windows is in English, the reference text changes, and in that case it's better to use: systeminfo | find /i “install”In this way, the command will search for the word "install" and return only the line that includes the information we want, ignoring the rest of the output.

This method is especially useful in corporate environments or servers where perhaps PowerShell is not commonly usedor where older CMD-based scripts are still used. In either case, the result is the same: a clear date that tells you when the operating system was installed in that specific team.

The Registry key with InstallDate and the Unix format

Behind all these commands, Windows stores the installation information in the system registrySpecifically, there is a key that stores the installation date in a format that is not directly readable at first glance, which explains why it is more convenient to use PowerShell or systeminfo.

That key lies in the route HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion, and within it the value that interests us is called InstallDateThe problem is that this value is not stored as a normal date, but in Unix format, that is, as a number representing the seconds elapsed since January 1, 1970.

If you open the Registry Editor (regedit) and navigate to that path, you'll see a seemingly strange number, something like a long, meaningless string. It's actually the Unix timestamp indicating the exact moment Windows was installed. To convert it to a readable date, you would need to use a Unix timestamp calculator or a script that performs the conversion to a standard date format.

For this reason, it is much more practical in everyday life. check the installation date using commands that already perform that conversion internallyBoth the PowerShell cmdlet and the systeminfo command take that InstallDate in Unix format and present it in a format that we can understand instantly.

Even so, knowing that the information is in the Registry can be useful if you like tinkering with advanced scripts, automations, or internal audits, especially in environments where you want to extract that date in bulk from several computers to keep track of installations.

History of major updates in Windows 10 and their effect on Windows 11

In Windows 10, and partly inherited in Windows 11 as well, the major operating system updates (These so-called "feature updates" or "mega-updates") are treated almost as if they were new installations. Every time you upgrade from one major version to another, the system creates additional internal entries in the Registry with its own installation date.

To consult that history, Windows uses the branch HKEY_LOCAL_MACHINE \ SYSTEM \ SetupWithin it you will find several subkeys, and those that begin with “Source OS” They correspond precisely to those major updates that have been applied to the equipment over time.

Each of these "Source OS" subkeys contains an InstallDate value, also in Unix format, indicating the date that specific version of the system was installed. So, if your PC started with, for example, Windows 10 Pro 1607 And then you went through 1703, 1709, 1803, etc., each of those big leaps will be reflected there along with the corresponding date.

From PowerShell, you can easily navigate through that part of the Registry using a slightly more advanced command. A typical option is to use: Get-ChildItem -Path HKLM:\System\Setup\Source* | ForEach-Object { Get-ItemProperty -Path Registry::$_ } | Select-Object ProductName, ReleaseID, CurrentBuild, @{n=»Install Date»;e={('1/1/1970').AddSeconds($_.InstallDate)}} | Sort-Object «InstallDate»This script iterates through all the "Source*" subkeys, extracts their information, and converts the Unix dates to normal date format.

The result is an ordered list where you can see, for each major version of Windows your computer has run, the product name, version identifier, build, and installation dateIt's a very powerful way to understand the evolution of the system over time and to know if what you considered the original installation is actually a major upgrade.

In that context, much documentation distinguishes between: 1) Windows installation date (current version)which is what you see with systeminfo or the basic cmdlet, and 2) Version historywhich you can reconstruct from these "Source OS" entries. Knowing how to differentiate between the two helps you correctly interpret what the dates you see when you query the system mean.

Limits on knowing when an app was installed or last used

When discussing specific programs, such as Avast One or other antivirus programs, there is a delicate issue: Windows 11 does not natively offer a complete record of the installation date, much less the last time each application was used.What you see in the Applications list within Settings usually corresponds to the date of the last major update, not the first installation.

Microsoft has confirmed that, in terms of features integrated into the system, There is no official function that clearly stores and displays the date and time of an app's last useBeyond the "Recent Apps" section of the Start menu or similar listings, which only reflect very recent usage, there is no detailed history accessible to the user.

This means that, although you may see a date associated with an app, in many cases it is simply the last update of the program or the date that package was modified on the system, not the day you first installed it. With antivirus and security suites, which are frequently updated, this discrepancy is practically the norm.

They exist, yes, specialized third-party applications which promise to offer finer monitoring of program installations and usage. However, due to support policies, Microsoft neither recommends nor can mention specific tools on its official channels, and always makes it clear that Any problems arising from the use of that software fall under the responsibility of the corresponding developer..

In practice, if you want to know whether a program like Avast came pre-installed or you installed it yourself, the most sensible thing to do is combine several clues: Windows installation date, the PC age, possible installer logs, service registration emails, digital invoices, etc. There is no "magic button" in Windows that says "this app was installed on day X and was last used on day Y".

It's important to keep in mind that, although the online ecosystem is enormous and there are almost certainly external tools to track these things, their use always involves some risk: They can collect data, affect performance, or cause conflicts with the systemIf you decide to go with one of them, it's a good idea to check reviews, documentation, and developer support before installing anything.

With all this information, it's finally possible to get a fairly concrete idea of How long has your Windows 11 installation been running, what is the "biological age" of your PC, and, if possible, how long have some key applications been with you?While you won't always get an exact date for every program, you will be able to better understand the temporal context of your system and make more informed decisions about maintenance, updates, or hardware changes.

Related articles:

How to find out the date of the last Windows 11 boot and usage history

Isaac

Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.