This morning, I was surprised to see that I needed to reboot my W10...
Pro computer in order to install an update. However, there it was.
This morning, I was surprised to see that I needed to reboot my W10 Pro computer in order to install an update. However, there it was.
Apparently, the update removes some old modem drivers and installs some
new Secure Boot certificates, as the older certificates hav recently
expired. The update is more fully described here:
https://support.microsoft.com/en-us/topic/january-13-2026-kb5073724-os-builds-19045-6809-and-19044-6809-bd960b49-050e-432f-a9d5-2454cb377fed
Here's what it says: ________________________________________________________________________
The following is a summary of the issues that this update addresses when
you install this update. If there are new features, it lists them as
well. The bold text within the brackets indicates the item or area of
the change we are documenting.
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys (x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[Secure Boot] Starting with this update, Windows quality updates
include a subset of high confidence device targeting data that
identifies devices eligible to automatically receive new Secure Boot certificates. Devices will receive the new certificates only after demonstrating sufficient successful update signals, ensuring a safe and phased deployment.
[WinSqlite3.dll] Fixed: The Windows core component, WinSqlite3.dll,
has been updated. Previously, some security software might have detected
this component as vulnerable.
Note: WinSqlite3.dll is a separate component from sqlite3.dll, which
is found in application-specific directories and is not a Windows
component. If security applications continue to detect sqlite3.dll as vulnerable, contact the developer of the app using sqlite3.dll for an
update. If sqlite3.dll is being used by a Microsoft app, install the
latest version of the app from the Microsoft Store. ________________________________________________________________________
Some people reported experiencing problems after installing the update:
https://www.reddit.com/r/Windows10/comments/1qc0860/microsoft_releases_windows_10_kb5073724_extended/
I allowed the update and, so far, have experienced no problems. Knock on wood.
This morning, I was surprised to see that I needed to reboot my W10 Pro computer in order to install an update. However, there it was.
Apparently, the update removes some old modem drivers and installs some
new Secure Boot certificates, as the older certificates hav recently
expired. The update is more fully described here:
https://support.microsoft.com/en-us/topic/january-13-2026-kb5073724-os-builds-19045-6809-and-19044-6809-bd960b49-050e-432f-a9d5-2454cb377fed
Here's what it says: ________________________________________________________________________
The following is a summary of the issues that this update addresses when
you install this update. If there are new features, it lists them as
well. The bold text within the brackets indicates the item or area of
the change we are documenting.
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys (x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[Secure Boot] Starting with this update, Windows quality updates
include a subset of high confidence device targeting data that
identifies devices eligible to automatically receive new Secure Boot certificates. Devices will receive the new certificates only after demonstrating sufficient successful update signals, ensuring a safe and phased deployment.
[WinSqlite3.dll] Fixed: The Windows core component, WinSqlite3.dll,
has been updated. Previously, some security software might have detected
this component as vulnerable.
Note: WinSqlite3.dll is a separate component from sqlite3.dll, which
is found in application-specific directories and is not a Windows
component. If security applications continue to detect sqlite3.dll as vulnerable, contact the developer of the app using sqlite3.dll for an
update. If sqlite3.dll is being used by a Microsoft app, install the
latest version of the app from the Microsoft Store. ________________________________________________________________________
Some people reported experiencing problems after installing the update:
https://www.reddit.com/r/Windows10/comments/1qc0860/microsoft_releases_windows_10_kb5073724_extended/
I allowed the update and, so far, have experienced no problems. Knock on wood.
John C. wrote on 1/16/2026 4:01 AM:
This morning, I was surprised to see that I needed to reboot my W10 Pro computer in order to install an update. However, there it was.
Apparently, the update removes some old modem drivers and installs some
new Secure Boot certificates, as the older certificates hav recently expired. The update is more fully described here:
https://support.microsoft.com/en-us/topic/january-13-2026-kb5073724-os-builds-19045-6809-and-19044-6809-bd960b49-050e-432f-a9d5-2454cb377fed
Here's what it says: ________________________________________________________________________ The following is a summary of the issues that this update addresses when you install this update. If there are new features, it lists them as
well. The bold text within the brackets indicates the item or area of
the change we are documenting.
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys (x86). Modem hardware dependent on these specific drivers will no longer work in Windows.
I allowed the update and, so far, have experienced no problems. Knock on wood.
Here's what it says:
[Drivers] This update removes the following modem drivers:r
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longe
work in Windows.
On 2026/1/16 11:1:12, John C. wrote:
[]
Here's what it says:
[]
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[]
I fail to see any point in removing drivers, and thus killing equipment;
what is the justification?
(Not that I've used a MoDem - other than the ones built into my "router"
- for years; just as a point of principle.)
If drivers are _replaced_, that's a different matter.
"J. P. Gilliver" <G6JPG@255soft.uk> wrote:
On 2026/1/16 11:1:12, John C. wrote:
[]
Here's what it says:
[]
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer >>> work in Windows.
[]
I fail to see any point in removing drivers, and thus killing equipment;
what is the justification?
(Not that I've used a MoDem - other than the ones built into my "router"
- for years; just as a point of principle.)
If drivers are _replaced_, that's a different matter.
If the drivers are no longer supported by the hardware maker, Microsoft doesn't want to be doling out or supporting old and possibly bad
drivers. They only distribute the drivers. They don't write them. The hardware might still be working, but that doesn't mean Microsoft wants
to proliferate bad or unsupported drivers for that still-working
hardware.
The agrsm[64].sys, I guessing are for some Agere hardware. Agere went defunct back in 2007. Merged into LSI Corp who went defunct in 2014. Acquired by Avago Tech in 2016, rebranded to Broadcom. Good luck
finding the drivers there.
Despite Microsoft removed them, you could reinstall them if you still
had the media (e.g., CD or floppy) that came with the product. Or get
them from the hardware maker, but I doubt Broadcom has them.
"J. P. Gilliver" <G6JPG@255soft.uk> wrote:
I fail to see any point in removing drivers, and thus killing equipment;
what is the justification?
If the drivers are no longer supported by the hardware maker, Microsoft doesn't want to be doling out or supporting old and possibly bad
drivers. They only distribute the drivers. They don't write them. The hardware might still be working, but that doesn't mean Microsoft wants
to proliferate bad or unsupported drivers for that still-working
hardware.
"John C." <r9jmg0@yahoo.com> wrote:
This morning, I was surprised to see that I needed to reboot my W10 Pro
computer in order to install an update. However, there it was.
Apparently, the update removes some old modem drivers and installs some
new Secure Boot certificates, as the older certificates hav recently
expired. The update is more fully described here:
https://support.microsoft.com/en-us/topic/january-13-2026-kb5073724-os-builds-19045-6809-and-19044-6809-bd960b49-050e-432f-a9d5-2454cb377fed
Here's what it says:
________________________________________________________________________
The following is a summary of the issues that this update addresses when
you install this update. If there are new features, it lists them as
well. The bold text within the brackets indicates the item or area of
the change we are documenting.
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[Secure Boot] Starting with this update, Windows quality updates
include a subset of high confidence device targeting data that
identifies devices eligible to automatically receive new Secure Boot
certificates. Devices will receive the new certificates only after
demonstrating sufficient successful update signals, ensuring a safe and
phased deployment.
[WinSqlite3.dll] Fixed: The Windows core component, WinSqlite3.dll,
has been updated. Previously, some security software might have detected
this component as vulnerable.
Note: WinSqlite3.dll is a separate component from sqlite3.dll, which
is found in application-specific directories and is not a Windows
component. If security applications continue to detect sqlite3.dll as
vulnerable, contact the developer of the app using sqlite3.dll for an
update. If sqlite3.dll is being used by a Microsoft app, install the
latest version of the app from the Microsoft Store.
________________________________________________________________________
Some people reported experiencing problems after installing the update:
https://www.reddit.com/r/Windows10/comments/1qc0860/microsoft_releases_windows_10_kb5073724_extended/
I allowed the update and, so far, have experienced no problems. Knock on
wood.
My concern is about the Secure Boot certificates. The KB article says
the certs will roll out based on criteria of eligible devices. So, this update doesn't have any certs. Those come later.
The eligibility was not well defined. It's based on some "signals" in further updates. Since Secure Boot is not currently enabled on my
computer, maybe I would be considered ineligible, and won't get the
certs in later updates. I am enrolled in ESU (Extended Service Updates) which ends October 2026.
I was planning on upgrading from Windows 10 to 11. TPM and Secure Boot
would get enabled in the BIOS before installing Windows 11, and
hopefully Windows 10 would get the new certs after the old ones expire. However, according to expirations listed at:
https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
Microsoft Corporation KEK CA 2011
June 2026
Signs updates to DB and DBX.
Microsoft Windows Production PCA 2011
Oct 2026
Used for signing the Windows boot loader.
Microsoft UEFI CA 2011*
June 2026
Signs third-party boot loaders and EFI applications.
Microsoft UEFI CA 2011*
June 2026
Signs third-party option ROMs
I don't what "DB and DBX" means other than some database, but what use I don't know. The boot loader for Windows seems the most important cert
update as the UEFI won't load it without a proper cert if Secure Boot is enabled.
So, maybe I should figure out how to install Windows 11 without Secure
Boot enabled, and forego any security therefrom. I installed and tested Windows 11 Pro as a guest OS inside a virtual machine using Rufus to eliminate the TPM, Secure Boot, and MS account requirements. That
worked, so maybe I'll do that for the Windows 11 upgrade in the real computer.
As for the reddit folks saying there are problems with this update:
- Breaks the taskbar
Unclear what "break" means. Mine still works after the update.
- Breaks functionality of the windows button on my keyboard
My Winkey still works.
- Made some apps very slow (even apps that should be very stable start
"Not responding" and never close)
Oh, some apps. If the poster knew that, he'd also know which ones.
- prevents my machine from fully restarting
What would be partial restarting? My reboots okay.
- my (important) Caller-ID application stopped working.
Probably due to the update removing old modem drivers. My guess is
that user has an analog modem for faxing, and maybe calling. No
mention he visited the hardware maker's website to get drivers. He
said he uninstalled the update, and his modem worked again. So,
install the update, and reinstall the modem drivers. If his modem is
so old that the maker no longer has drivers, well, he could get a new
dial-up modem. RS-232 modems are harder to find, and we don't know if
he uses an external modem to a serial port, or a USB modem, or a
daughtercard in a mobo slot.
Those folks could revert to the prior state using their image backups.
Oops, there's another deer caught in headlights. System Restore should
work, too, since Windows updates saves a restore point before installing
an update.
It isn't just this update. Any Windows, program, app, or driver update
can cause problems. Be prepared BEFORE updating. I rely on image
backups to restore. System Restore is a bit iffy.
On 2026/1/16 11:1:12, John C. wrote:
[]
Here's what it says:
[]
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[]
I fail to see any point in removing drivers, and thus killing equipment;
what is the justification?
(Not that I've used a MoDem - other than the ones built into my "router"
- for years; just as a point of principle.)
If drivers are _replaced_, that's a different matter.
Security Vulnerability:l
The primary reason was a severe privilege escalation flaw
(CVE-2025-24990) in the Agere modem driver, which was present across al
Windows versions.it
Legacy Code:
The driver was outdated, predating modern security practices, making
a significant systemic risk.
Microsoft's Action:
Instead of patching the risky legacy component, Microsoft chose to
remove it entirely from Windows.
On 2026/1/17 1:44:37, ...w¤?ñ?¤ wrote:
[]
Security Vulnerability:
The primary reason was a severe privilege escalation flaw
(CVE-2025-24990) in the Agere modem driver, which was present across all
Windows versions.
Legacy Code:
The driver was outdated, predating modern security practices, making it >> a significant systemic risk.
Microsoft's Action:
Instead of patching the risky legacy component, Microsoft chose to
remove it entirely from Windows.
Surely it'd be better to pop up a warning, giving the user the _option_
of removing the affected driver(s) - or, even, the option of keeping it (making removal the default). Rather than just killing it.
On 2026/1/17 1:44:37, ...w¤?ñ?¤ wrote:
[]
Security Vulnerability:
The primary reason was a severe privilege escalation flaw
(CVE-2025-24990) in the Agere modem driver, which was present across all
Windows versions.
Legacy Code:
The driver was outdated, predating modern security practices, making it >> a significant systemic risk.
Microsoft's Action:
Instead of patching the risky legacy component, Microsoft chose to
remove it entirely from Windows.
Surely it'd be better to pop up a warning, giving the user the _option_
of removing the affected driver(s) - or, even, the option of keeping it (making removal the default). Rather than just killing it.
VanguardLH <V@nguard.LH> wrote:
"John C." <r9jmg0@yahoo.com> wrote:
This morning, I was surprised to see that I needed to reboot my W10 Pro
computer in order to install an update. However, there it was.
Apparently, the update removes some old modem drivers and installs some
new Secure Boot certificates, as the older certificates hav recently
expired. The update is more fully described here:
https://support.microsoft.com/en-us/topic/january-13-2026-kb5073724-os-builds-19045-6809-and-19044-6809-bd960b49-050e-432f-a9d5-2454cb377fed
Here's what it says:
________________________________________________________________________ >>> The following is a summary of the issues that this update addresses when >>> you install this update. If there are new features, it lists them as
well. The bold text within the brackets indicates the item or area of
the change we are documenting.
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer >>> work in Windows.
[Secure Boot] Starting with this update, Windows quality updates
include a subset of high confidence device targeting data that
identifies devices eligible to automatically receive new Secure Boot
certificates. Devices will receive the new certificates only after
demonstrating sufficient successful update signals, ensuring a safe and
phased deployment.
[WinSqlite3.dll] Fixed: The Windows core component, WinSqlite3.dll,
has been updated. Previously, some security software might have detected >>> this component as vulnerable.
Note: WinSqlite3.dll is a separate component from sqlite3.dll, which >>> is found in application-specific directories and is not a Windows
component. If security applications continue to detect sqlite3.dll as
vulnerable, contact the developer of the app using sqlite3.dll for an
update. If sqlite3.dll is being used by a Microsoft app, install the
latest version of the app from the Microsoft Store.
________________________________________________________________________ >>>
Some people reported experiencing problems after installing the update:
https://www.reddit.com/r/Windows10/comments/1qc0860/microsoft_releases_windows_10_kb5073724_extended/
I allowed the update and, so far, have experienced no problems. Knock on >>> wood.
My concern is about the Secure Boot certificates. The KB article says
the certs will roll out based on criteria of eligible devices. So, this
update doesn't have any certs. Those come later.
The eligibility was not well defined. It's based on some "signals" in
further updates. Since Secure Boot is not currently enabled on my
computer, maybe I would be considered ineligible, and won't get the
certs in later updates. I am enrolled in ESU (Extended Service Updates)
which ends October 2026.
I was planning on upgrading from Windows 10 to 11. TPM and Secure Boot
would get enabled in the BIOS before installing Windows 11, and
hopefully Windows 10 would get the new certs after the old ones expire.
However, according to expirations listed at:
https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
Microsoft Corporation KEK CA 2011
June 2026
Signs updates to DB and DBX.
Microsoft Windows Production PCA 2011
Oct 2026
Used for signing the Windows boot loader.
Microsoft UEFI CA 2011*
June 2026
Signs third-party boot loaders and EFI applications.
Microsoft UEFI CA 2011*
June 2026
Signs third-party option ROMs
I don't what "DB and DBX" means other than some database, but what use I
don't know. The boot loader for Windows seems the most important cert
update as the UEFI won't load it without a proper cert if Secure Boot is
enabled.
So, maybe I should figure out how to install Windows 11 without Secure
Boot enabled, and forego any security therefrom. I installed and tested
Windows 11 Pro as a guest OS inside a virtual machine using Rufus to
eliminate the TPM, Secure Boot, and MS account requirements. That
worked, so maybe I'll do that for the Windows 11 upgrade in the real
computer.
As for the reddit folks saying there are problems with this update:
- Breaks the taskbar
Unclear what "break" means. Mine still works after the update.
- Breaks functionality of the windows button on my keyboard
My Winkey still works.
- Made some apps very slow (even apps that should be very stable start
"Not responding" and never close)
Oh, some apps. If the poster knew that, he'd also know which ones.
- prevents my machine from fully restarting
What would be partial restarting? My reboots okay.
- my (important) Caller-ID application stopped working.
Probably due to the update removing old modem drivers. My guess is
that user has an analog modem for faxing, and maybe calling. No
mention he visited the hardware maker's website to get drivers. He
said he uninstalled the update, and his modem worked again. So,
install the update, and reinstall the modem drivers. If his modem is
so old that the maker no longer has drivers, well, he could get a new
dial-up modem. RS-232 modems are harder to find, and we don't know if
he uses an external modem to a serial port, or a USB modem, or a
daughtercard in a mobo slot.
Those folks could revert to the prior state using their image backups.
Oops, there's another deer caught in headlights. System Restore should
work, too, since Windows updates saves a restore point before installing
an update.
It isn't just this update. Any Windows, program, app, or driver update
can cause problems. Be prepared BEFORE updating. I rely on image
backups to restore. System Restore is a bit iffy.
Well, I did encounter an anomaly, but it may incidental. After a cold
boot, my video was at much lower resolution (1280x1024). I rebooted a
couple times more, let it boot into Windows, and restarted, but was
still at a low resolution. The card and monitor should be 2560x1440. Reinstalled the video driver, and was 2560x1440 after a reboot.
Can't say this was caused by this update. I was putzing with memory
module configuration. When I ran the video driver installer, it
reported the video card did not start on the prior reboot, and had me
fill out a report to send to AMD. I'm guessing the onboard video in the
CPU got used hence the lower resolution. That's why I checked BIOS to
ensure the primary video was set to PCIe, and not onboard. In fact, I changed to from PCIe to onboard back to PCIe just to ensure the setting
got stepped on. No joy until I reinstalled the video driver, and
another reboot. Guess my computer decided I got too complacent
regarding its care. Feed me, feed me. Possibly the new update. It's getting to be all FM: Fucking Magic.
Didn't anyone else reporting KB5073724 cause a video problem, so it is probably an incidental problem. Sure woke we up.
John C. wrote:
[]
Here's what it says:
[]
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys
(x86). Modem hardware dependent on these specific drivers will no longer
work in Windows.
[]
I fail to see any point in removing drivers, and thus killing equipment;
what is the justification?
(Not that I've used a MoDem - other than the ones built into my "router"
- for years; just as a point of principle.)
If drivers are _replaced_, that's a different matter.
- items have been removed and deprecated and complained or agreed upon
for decades.
On 2026/1/17 8:12:46, ...w??? wrote:
[]
- items have been removed and deprecated and complained or agreed upon for decades.
[]
I deprecate anyone (or -think) who/that deprecates. On the whole, I
deprecate any that even uses the word, which I didn't come across until
in the software context (at first in HTML, IIRR).
Always a PITA to have to go through these kinds of hoops due to an
update. My ancient (but loved) desktop is running an NVIDIA GeForcce GT
1030 card. The installed driver wants to call home for updates, but I
block it in my firewall from doing so.
On 2026/1/17 0:21:33, VanguardLH wrote:
"J. P. Gilliver" <G6JPG@255soft.uk> wrote:
On 2026/1/16 11:1:12, John C. wrote:
[]
Here's what it says:
[]
[Drivers] This update removes the following modem drivers:
agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys >>>> (x86). Modem hardware dependent on these specific drivers will no longer >>>> work in Windows.
[]
I fail to see any point in removing drivers, and thus killing equipment; >>> what is the justification?
(Not that I've used a MoDem - other than the ones built into my "router" >>> - for years; just as a point of principle.)
If drivers are _replaced_, that's a different matter.
If the drivers are no longer supported by the hardware maker, Microsoft
doesn't want to be doling out or supporting old and possibly bad
drivers. They only distribute the drivers. They don't write them. The
hardware might still be working, but that doesn't mean Microsoft wants
to proliferate bad or unsupported drivers for that still-working
hardware.
There's a difference between not proliferating them, and actively
withdrawing them.
The agrsm[64].sys, I guessing are for some Agere hardware. Agere went
defunct back in 2007. Merged into LSI Corp who went defunct in 2014.
Acquired by Avago Tech in 2016, rebranded to Broadcom. Good luck
finding the drivers there.
Despite Microsoft removed them, you could reinstall them if you still
had the media (e.g., CD or floppy) that came with the product. Or get
them from the hardware maker, but I doubt Broadcom has them.
As I said, I'm not using any of the affected hardware; it's more the principle.
Indeed! 'deprecate' has no positive or even just neutral connotation
that I know of.
There's a second meaning: "To belittle; depreciate." Fowler calls
this a "blunder," and I agree.
John C. wrote:
Always a PITA to have to go through these kinds of hoops due to an
update. My ancient (but loved) desktop is running an NVIDIA GeForcce GT
1030 card. The installed driver wants to call home for updates, but I
block it in my firewall from doing so.
The custom settings on the NVidia driver (as downloaded from NVidia
and not from Windows Update), allows un-ticking Geforce Experience,
and that may result in a reduction in network traffic.
At one time, scheduled tasks had some NVidia entries, and removing
those can reduce the calling home too.
Stan Brown wrote:
There's a second meaning: "To belittle; depreciate." Fowler calls
this a "blunder," and I agree.
Fowler is right; "depreciate" is not generally used to mean belittle.
In English (as opposed to American) "depreciate" means to reduce in
value, which is what happens to your currency when it suffers from inflation, or your car's value as it gets older.
Maybe American has an alternative definition?
Graham J <nobody@nowhere.co.uk> wrote:
Stan Brown wrote:
There's a second meaning: "To belittle; depreciate." Fowler calls
this a "blunder," and I agree.
What would you use as the converse or antonym of appreciate? Un prefix
could be used, as in unappreciate, but the de prefix also means
For computers: to cease supporting or recommending the use of (older elements, features, or versions of software).
In English (as opposed to American) "depreciate" means to reduce in
value, which is what happens to your currency when it suffers from inflation, or your car's value as it gets older.
v.tr.
1. To lessen the price or value of: An increase in the supply of
money depreciated the currency.
2. To write off an expenditure for (a tangible asset) by
prorating over a certain period, usually the estimated useful
life of the asset.
3. To think or speak of as being of little worth; belittle. See
Synonyms at disparage. See Usage Note at deprecate.
v.intr.
To diminish in price or value: "When issued in excess, as during
the Revolution, paper depreciated in value" (Daniel Feller).
What would you use as the converse or antonym of appreciate? Un prefix could be used, as in unappreciate, but the de prefix also means
I think I'd use "not appreciate" - two words - or another phrase.
Difficult to say without context.
Maybe American has an alternative definition?
https://www.dictionary.com/browse/deprecate
For people: to disapprove or belittle them.
For computers: to cease supporting or recommending the use of (older elements, features, or versions of software).
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 15 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 06:33:19 |
| Calls: | 188 |
| Files: | 21,502 |
| Messages: | 81,815 |