![]() |
MS-DEFCON 2:
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it.
|
-
Patch Lady – KB4088875 more questions
Home › Forums › AskWoody blog › Patch Lady – KB4088875 more questions
Tagged: KB 4088875, Patch Lady Posts
- This topic has 43 replies, 15 voices, and was last updated 3 years ago by
anonymous.
Viewing 21 reply threads-
AuthorPosts
-
-
March 27, 2018 at 3:23 pm #178472
Susan Bradley
ManagerThe following update has been updated KB4088875 but in doing so I’m scratching my head a bit more. Remember our original side effects relate to netwo
[See the full post at: Patch Lady – KB4088875 more questions]Susan Bradley Patch Lady
-
March 27, 2018 at 3:42 pm #178483
alpha128
AskWoody Plus-
March 27, 2018 at 4:20 pm #178498
Susan Bradley
Manager-
March 28, 2018 at 2:39 am #178627
anonymous
GuestThe timestamp on the update in the catalogue (https://www.catalog.update.microsoft.com/Search.aspx?q=4088875) is still March 14th. So not much updating there …
-
-
-
March 27, 2018 at 4:17 pm #178495
PKCano
ManagerRunning scripts and geeky bail-outs are not for the average Joe User who probably has WU on Automatic.. I hope they don’t put this back on WU until they get the bugs ironed out.
It has disappeared completely from WU on all of my VMs as well as four hardware installs. It doesn’t show up at all.
-
March 27, 2018 at 4:26 pm #178500
SkipH
AskWoody Plus@PatchLady:
It also appears that the issues you mention in this thread might also apply to KB4088878 (2018-03 Security-only update), used by members of Woody’s “Group B update” process.
I have checked the MS web page for KB7088878, and it has the same prerequisites and VB script as KB4088875.
Information on KB7088878 does not list the problem with IE 11, as that sub-patch is not included in KB7088878.
Since there are still a number of us patching ‘hold-outs’ that are in the B-Group, I think that KB7088878 needs to be mentioned in this thread, as it appears to be subject to the same problems as KB4088875.
-
March 27, 2018 at 4:28 pm #178501
Elly
AskWoody MVPIt showed up initially, and I hid it. There were some reports that it was not being seen, or that the check mark had disappeared. Think that was on the 15th. I unhid it, and it disappeared. It hasn’t shown up in my Windows Update since… not unchecked… not at all.
Non-techy Win 10 Pro and Linux Mint experimenter
-
March 27, 2018 at 4:42 pm #178502
Susan Bradley
ManagerIt’s still out on Microsoft update, it is unchecked however and thus not being pushed out, but it’s not been “pulled”. When it’s pulled it then is removed from WSUS and the catalog. When you hide it unless there is a detection change pushed by Microsoft it will stay hidden.
Susan Bradley Patch Lady
-
March 27, 2018 at 5:29 pm #178518
Bill C.
AskWoody PlusI am on WIn7-64_SP1, with WU set to Do not check. I initiate all checks manually and follow Woody’s Group B patching for the Monthly Security Only and the IE Rollup.
I originally had the March 2018 Security and Quality Rollup KB4088875 in my Windows Update as checked. I did not install it, nor did I hide it. I just closed WU to wait for the Defcon change.
SInce that intial view however, it has never appeared again. All I see is last months February 2018 Security and Quality Rollup KB4074598 as Important and checked. In February I did install the February Security Only KB4074587 from the catalog.
To further complicate th issue, my Intel-brand motherboard has both the Intel® 82567L and Intel® 82574L Gigabit Ethernet Controllers onboard. These both are listed as apparently being vulnerable to having their NIC settings wiped by the March Rollup AND the Security Only patches. Coincidently, Intel has just released (2/22/2018) new drivers for these controllers, but the controllers are listed as Legacy status, and there is no mention about them fixing the March Rollup issues. From experience, I do not usually mess with working network drivers unless it is a security issue or I am having a problem.
My main question is if the March KBs are not even showing on the WU on my machine now, either checked or unchecked, will they ever be, or would a fix come next month. However with a Security Only, NOT being a rollup, what is the implications for a Group B to miss a problematic month.
-
-
-
March 27, 2018 at 5:19 pm #178513
Seff
AskWoody PlusIt remains unchecked on my two home machines, and therefore will not be installed until it becomes checked and there is a recommendation here to accept it. There is no question at that time of my fiddling with the registry or VBScript (whatever that is), either it’s ready to be installed through WU or it doesn’t get installed.
1 user thanked author for this post.
-
March 27, 2018 at 6:08 pm #178535
pmcjr6142
AskWoody PlusSusan, someone wrote this comment…”It remains unchecked on my two home machines, and therefore will not be installed until it becomes checked and there is a recommendation here to accept it. There is no question at that time of my fiddling with the registry or VBScript (whatever that is), either it’s ready to be installed through WU or it doesn’t get installed.”
These are my sentiments exactly. There is no way I want to even try the work around you mention, ie, registry and/or VBS script. I’m just a moderately computer literate senior who follows Ask Woody and not you. It has been unchecked on my Win 7 machine for several days. Do you recommend we just hide it and wait for something to replace it next month? With the problems that accompany KB4088875, I can’t see you or Woody coming to a different conclusion and say go ahead and install it.
Thank you.
Edit to remove HTML. Please use the “text” tab in the entry box when you copy/paste.
-
March 27, 2018 at 6:38 pm #178543
MrBrian
AskWoody_MVP-
March 27, 2018 at 7:54 pm #178558
MrBrian
AskWoody_MVPHere is the older script, in case anybody wants to compare:
Option Explicit Const HKEY_LOCAL_MACHINE = &H80000002 Dim oReg : Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv") Dim oShell : Set oShell = CreateObject("WScript.Shell") Dim sPath, aSub, sKey, aSubToo, sKeyToo, dwValue, Result, SaveResult Dim NotDeleted NotDeleted = 0 ' Get all keys within sPath sPath = "SYSTEM\CurrentControlSet\Enum\PCI" oReg.EnumKey HKEY_LOCAL_MACHINE, sPath, aSub ' Loop through each key For Each sKey In aSub ' Get all subkeys within the key 'sKey' oReg.EnumKey HKEY_LOCAL_MACHINE, sPath & "\" & sKey, aSubToo For Each sKeyToo In aSubToo Result = oReg.DeleteKey(HKEY_LOCAL_MACHINE, sPath & "\" & sKey & "\" & sKeyToo & "\" & "\Device Parameters" & "\SlotPersistentInfo") ' Allow failure only if key never existed If (Result = 1) Or (Result > 2) Then NotDeleted = 1 SaveResult = Result End If Next Next If (NotDeleted > 0) Then Wscript.Echo "One or more SlotPersistentInfo keys still exist under HKLM\System\CurrentControlSet\Enum\PCI\<deviceid>\<subdeviceid>\Device Parameters. Please delete manually. Result = " & Result End If
Here is the current script (in case it changes again in the future):
Dim strPciFileVersion Dim WindirFilePath set WshShell = WScript.CreateObject("WScript.Shell") WindirFilePath = WshShell.ExpandEnvironmentStrings("%WinDir%") Dim fs Set fs = CreateObject("Scripting.FileSystemObject") strPciFileVersion = fs.getfileversion(WindirFilePath & "\\system32\\drivers\\pci.sys") Dim strAryFileVersion1 strAryFileVersion1 = Split(strPciFileVersion, ".") If (strAryFileVersion1(0) = 6 And strAryFileVersion1(1) = 1 And strAryFileVersion1(2) = 7601) Then If (strAryFileVersion1(3) < 17630 Or (strAryFileVersion1(3) > 20000 And strAryFileVersion1(3) < 21744)) Then Const HKEY_LOCAL_MACHINE = &H80000002 Dim oReg : Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv") Dim oShell : Set oShell = CreateObject("WScript.Shell") Dim sPath, aSub, sKey, aSubToo, sKeyToo, dwValue, Result, SaveResult Dim NotDeleted NotDeleted = 0 ' Get all keys within sPath sPath = "SYSTEM\CurrentControlSet\Enum\PCI" oReg.EnumKey HKEY_LOCAL_MACHINE, sPath, aSub ' Loop through each key For Each sKey In aSub ' Get all subkeys within the key 'sKey' oReg.EnumKey HKEY_LOCAL_MACHINE, sPath & "\" & sKey, aSubToo For Each sKeyToo In aSubToo Result = oReg.DeleteKey(HKEY_LOCAL_MACHINE, sPath & "\" & sKey & "\" & sKeyToo & "\" & "\Device Parameters" & "\SlotPersistentInfo") ' Allow failure only if key never existed If (Result = 1) Or (Result > 2) Then NotDeleted = 1 SaveResult = Result End If Next Next If (NotDeleted > 0) Then Wscript.Echo "SlotPersistentInfo keys still exist under HKLM\System\CurrentControlSet\Enum\PCI\<deviceid>\<subdeviceid>\Device Parameters. Please delete all manually and then install the updates. Result = " & Result End If Else WScript.Echo "Your system is ready to install the updates" End If Else WScript.Echo "Your system is ready to install the updates" End If
1 user thanked author for this post.
-
March 27, 2018 at 8:09 pm #178566
-
-
March 28, 2018 at 12:52 am #178618
abbodi86
AskWoody_MVPHere is a slightly enhanced version of the newly modified script
https://pastebin.com/HKwLHBJcit checks for and request Admin elevation, and display result as message box, so it can be ran by double-click
1 user thanked author for this post.
-
March 28, 2018 at 2:35 am #178629
-
-
March 27, 2018 at 7:07 pm #178544
MrBrian
AskWoody_MVPI did some sleuthing on my Windows 7 x64 virtual machine, which is not offered KB4088875 in Windows Update. (I have the QualityCompat registry setting set.) I turned on verbose Windows Update logging by using the program at How to Enable Microsoft Installer logging and Verbose logging to gather additional troubleshooting Information; this program sets different verbose settings than those documented at How to read the Windowsupdate.log file. Then I ran Windows Update on the virtual machine.
I then searched log file \windows\Windowsupdate.log for 4088875 and also 26896846-497d-4755-893a-6870f72ddcf4 (its Update ID for Windows 7 x64, which can be found by looking in the Catalog). Three interesting things that I found in Windowsupdate.log related to this update:
1) ‘Final detection state for update 26323815 (updateId = {26896846-497D-4755-893A-6870F72DDCF4}.200) is “Installable”‘. This I what I expected to see for this update. This means that KB4088875 isn’t installed on the computer, and that it’s applicable to be installed on the computer.
2) ‘update {26896846-497D-4755-893A-6870F72DDCF4}.200 marked for pruning because of its deployment attribute supersedenceBehavior=1’. The phrase ‘marked for pruning because of its deployment attribute supersedenceBehavior=1’ appears only one other time in Windowsupdate.log, for update 3B785578-FF3C-4C49-BB6D-D6F9D2688503, which is KB4091290; I mentioned in another topic that KB4091290 has supersedence behavior that surprised me. I searched the web for documentation about supersedenceBehavior, but found nothing useful. It’s far more common to see ‘marked for pruning because it is potentially superseded’ in Windowsupdate.log (found 1201 times).
3) ‘Update {26896846-497D-4755-893A-6870F72DDCF4}.200 is pruned out due to potential supersedence’. But why, given that the Catalog notes that there are no updates currently metadata-superseding KB4088875? I hypothesize that this is related to the unusual supersedenceBehavior setting for KB4088875 noted in the last paragraph.
-
March 27, 2018 at 7:22 pm #178549
-
March 27, 2018 at 7:49 pm #178556
MrBrian
AskWoody_MVPI am curious if those who have KB4088875 listed in Windows Update see ‘update {26896846-497D-4755-893A-6870F72DDCF4}.200 marked for pruning because of its deployment attribute supersedenceBehavior=1’ (without the quotes) in their verbose-enabled Windowsupdate.log.No longer curious! 😀
1 user thanked author for this post.
-
March 28, 2018 at 10:19 am #178702
-
-
March 27, 2018 at 7:39 pm #178553
MrBrian
AskWoody_MVP“2. Can an admin run this script before the install of the update? (based on admins testing this it appears the answer is yes)
3. In a consumer setting, where we only go to Windows update, do we need this? (I don’t think so but it would be nice to know for sure)”The KB article states (my bolding):
“Prerequisites
Follow these steps before you apply this update to a physical computer or a virtual machine:”
My answer for both point number 2 and 3 is yes, and furthermore running the script beforehand is seemingly mandatory for all users who intend to install KB4088875 or KB4088878.
-
March 27, 2018 at 8:31 pm #178574
geekdom
AskWoody PlusHow likely is it that Microsoft will include the script in the final release update?
On Hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 20H2.19042.804 x64 i5-9400 RAM16GB HDD Firefox86.0 WindowsDefender TRV=20H2 WuMgr-
March 27, 2018 at 8:43 pm #178579
-
-
-
March 27, 2018 at 8:22 pm #178570
MrBrian
AskWoody_MVPReport from a reddit user: From https://www.reddit.com/r/sysadmin/comments/84n3cy/microsoft_released_a_script_to_preventrepair/dvrcrf8/:
“It may do only that after the fact, but if you apply it before patching then it does prevent the issue with the NIC reverting to prior settings (be they DHCP or static) from happening in the first place. I’ve verified this on a test machine by taking a snapshot of it and then applying this month’s patches both with and without running the script first (reverting to the pre update snapshot in between).”
-
March 27, 2018 at 8:38 pm #178576
MrBrian
AskWoody_MVPIf the info on reddit is accurate, then I infer that:
1. If you didn’t run the script before installing the update, and you have NIC (Network Interface Card) problems afterwards, then you need to run the older script afterwards, and then manually fix whatever undesirably changed in the affected NIC settings.
2. If you run the script before installing the update, you will not have any NIC problems after installing the update.
-
March 27, 2018 at 10:08 pm #178595
-
-
-
March 27, 2018 at 8:29 pm #178573
MrBrian
AskWoody_MVPTip: Since the script’s fixes (if needed) delete items from a part of the registry that usually needs admin privileges for such actions, you probably need to run the script with admin privileges. If you run the script without admin privileges, it should not be able to apply the fixes, but it should at least report if fixes are needed or not. In other words, running the script without admin privileges should give useful info but without successfully applying any needed fixes.
-
March 27, 2018 at 9:32 pm #178589
MrBrian
AskWoody_MVPIf I’m correct that the script needs admin privileges, you can do so by following method 1 at http://sigkillit.com/2013/01/26/running-vbscripts-with-uac-elevation/.
1 user thanked author for this post.
-
March 27, 2018 at 10:51 pm #178600
MrBrian
AskWoody_MVPI have confirmed in a test that admin privileges are needed to fix the issue if it’s present. If you don’t run the script with admin privileges, and you have the NIC issue, you should get a message similar to “SlotPersistentInfo keys still exist […]”.
1 user thanked author for this post.
-
-
March 27, 2018 at 9:00 pm #178582
MrBrian
AskWoody_MVPFor those that already installed the update without running the script beforehand, there are steps to fix the NIC issue at RUSH POST: Microsoft Convenience Update, KB4088875 and KB4088878 vNIC Incompatibilities:
“ACTION: If you have been impacted, please note that the following manual fixes have been known to resolve the issue (after the fact):
- Note the name of the new network adapter
- Open “Device Manager” -> “Show Hidden Devices” and delete ALL hidden/phantom network adapters from the list (be sure to NOT delete the drivers)
- Edit the properties of the new NIC and add the applicable IP address configuration. No reboot is required.”
-
March 27, 2018 at 9:26 pm #178588
MrBrian
AskWoody_MVPThe newer script appears to have a few bugs that can result in the script giving no information messages instead of the intended message “Your system is ready to install the updates”. However, I believe that the script likely correctly always reports that there are unfixed NIC issues if that’s indeed the case.
Thanks to the user who informed me about this via private message.
-
March 27, 2018 at 9:49 pm #178593
-
-
March 27, 2018 at 11:45 pm #178608
abbodi86
AskWoody_MVP-
March 28, 2018 at 12:34 am #178615
Susan Bradley
Manager -
March 28, 2018 at 7:02 am #178654
ch100
AskWoody_MVPThis looks very much like when installing virtualisation tools which create a new emulated or paravirtual NIC. VMware handles this better, but it is very visible with Citrix XenServer.
I think (without experiencing the issue directly, but based on description only) that it can be resolved by enabling View Hidden Devices in Device Manager and delete/uninstall the phantom devices. I can elaborate on this, but this is not something for the most common askwoody.com reader and certainly DHCP configuration makes this transition more graceful for the end-user.
However, there is no excuse for an update to cause this behaviour, unless maybe in the case of Microsoft’s own (Hyper-V) Virtual Machines.
This is certainly not something that an end-user should have to resolve, but if the same end-user uses virtual machines, then it is a different story.EDIT: Windows 7 and 2008 R2 should be discontinued by now and everyone using them should plan and move away as fast as possible. It is obvious that there is not much effort from Microsoft in supporting them and those who insist on staying on those OSes do so on their own risk and headaches. There is no optimal option, either installing poor updates or not installing any updates at all.
-
March 28, 2018 at 7:27 am #178658
MrBrian
AskWoody_MVPTechnical details: Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078).
1 user thanked author for this post.
-
March 28, 2018 at 8:09 am #178675
ch100
AskWoody_MVPFrom the VMware KB article:
Windows 2008 R2 and Windows 7 track PCI devices by which slot the device is connected to. Moving a PCI network interface between slots will allocate a new set of settings for the NIC as it is considered a new device.This virtual slot concept in vSphere creates a lot of issues with PXE boot, common with virtual desktop solutions, when the slot changes. The NIC is simply not recognised anymore and as consequence the boot is not happening generating a BSOD.
1 user thanked author for this post.
-
-
-
-
March 28, 2018 at 8:22 am #178677
Mr. Natural
AskWoody Plus -
March 28, 2018 at 11:33 am #178722
DennyC
AskWoody LoungerI initially allowed KB4088875 to install on my two older Win 7 Pro SP1 machines and right away noticed slow boot times…like it was taking twice to three times as long to boot. I uninstalled the update and things are back to normal. So I’m in a holding pattern at the moment. Windows Update shows KB4088875 as available, but unchecked. Note: my normal boot time is around 45 seconds to a minute.
1 user thanked author for this post.
-
March 29, 2018 at 4:44 am #178856
-
March 29, 2018 at 8:53 am #178929
MrBrian
AskWoody_MVPI have concerns that due to the new script’s pci.sys version checking, those who have already installed the Windows 7 March 2018 updates cannot successfully use the new script if you’ve already rebooted. The Windows 7 March 2018 updates install version 6.1.7601.24056 of pci.sys. Here is the version check in the new script:
If (strAryFileVersion1(0) = 6 And strAryFileVersion1(1) = 1 And strAryFileVersion1(2) = 7601) Then If (strAryFileVersion1(3) < 17630 Or (strAryFileVersion1(3) > 20000 And strAryFileVersion1(3) < 21744)) Then
It appears that those with version 6.1.7601.24056 of pci.sys will not pass the second if statement, and thus the fixing code will not execute.
The old script, which doesn’t contain the pci.sys version check, is at https://www.askwoody.com/forums/topic/kb4088875-more-questions/#post-178558.
-
March 29, 2018 at 9:12 am #178936
MrBrian
AskWoody_MVPThe phrasing of the NIC issue has changed in two of the three Windows 7 March 2018 updates:
Old: “A new Ethernet virtual Network Interface Card (vNIC) that has default settings may replace the previously existing vNIC, causing network issues after you apply this update. Any custom settings on the previous vNIC persist in the registry but are unused.”
New: “After you apply this update, a new Ethernet Network Interface Card (NIC) that has default settings may replace the previous NIC and cause network issues. Any custom settings on the previous NIC persist in the registry but aren’t used.”
Microsoft is thus acknowledging that the NIC issue also can involve non-virtual NICs.
-
March 30, 2018 at 5:29 pm #179465
MrBrian
AskWoody_MVP“Microsoft has released update KB4099950” (“Network Interface Card settings can be replaced, or static IP address settings can be lost”)
1 user thanked author for this post.
-
April 13, 2018 at 3:52 am #184332
anonymous
GuestHi, I tested KB4099950 on several servers that don´t have the march patches yet.
on all of them the SlotPersistentInfo Reg keys where still in place after the KB was installed.I tried to install March patches after that and the nic info got lost.
Do anybody have an idea why the KB is not working for me?
If I manual run the .vbs with pci.sys version checking the keys get deleted and the March patches get installed without problems.
1 user thanked author for this post.
-
-
AuthorPosts
Viewing 21 reply threads - This topic has 43 replies, 15 voices, and was last updated 3 years ago by
-
Welcome to our unique respite from the madness.
It's easy to post questions about Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Questions? Contact Customer Support.

Plus Membership
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments. Click here for details and to sign up.
Search Newsletters
Search Forums
Recent Replies
F A Kramer on Patch Tuesday poll – how is the testing going?
Just nowLHiggins on Question about allowing/stopping laptop from turning off USB device
5 minutes agoAlex5723 on Ongoing List of Mac Apps Updated for Universal/Apple Silicon Support
9 minutes agoSky on Tips to protect a Laptop without battery?
12 minutes agoMoonshine on 20H2 Printer Queue Icon now missing from Task Bar
27 minutes agoOscarCP on Ongoing List of Mac Apps Updated for Universal/Apple Silicon Support
36 minutes agoanonymous on Outlook cannot read the calendar
40 minutes agoAlex5723 on Patch Tuesday poll – how is the testing going?
43 minutes agoSusan Bradley on MS-DEFCON 2 – Deferring the April Updates
49 minutes agoanonymous on Upgrade Firefox…recommendations please.
52 minutes agoTex265 on 20H2 Printer Queue Icon now missing from Task Bar
1 hour, 4 minutes agoSproots on MS-DEFCON 2 – Deferring the April Updates
1 hour, 20 minutes agoAlex5723 on Ongoing List of Mac Apps Updated for Universal/Apple Silicon Support
1 hour, 20 minutes agoWCHS on Patch Tuesday poll – how is the testing going?
1 hour, 25 minutes agoGraham on DPC WATCHDOG VIOLATION during upgrade
1 hour, 52 minutes agoSusan Bradley on Outlook cannot read the calendar
1 hour, 53 minutes agolmacri on New smartphone? Great! Now don’t charge it past 80%
1 hour, 57 minutes agolmacri on New smartphone? Great! Now don’t charge it past 80%
2 hours, 15 minutes agoCAS on April Patch Tuesday out – Exchange once again
2 hours, 17 minutes agob on DPC WATCHDOG VIOLATION during upgrade
2 hours, 28 minutes agoanonymous on Outlook cannot read the calendar
2 hours, 32 minutes agob on Computer suddenly shows in home network as media device
2 hours, 32 minutes agoPKCano on MS-DEFCON 2 – Deferring the April Updates
3 hours, 17 minutes agojoep517 on MS-DEFCON 2 – Deferring the April Updates
3 hours, 28 minutes agoPKCano on April Patch Tuesday out – Exchange once again
3 hours, 30 minutes agob on April Patch Tuesday out – Exchange once again
3 hours, 38 minutes agojoep517 on April Patch Tuesday out – Exchange once again
3 hours, 46 minutes agodoriel on April Patch Tuesday out – Exchange once again
3 hours, 55 minutes agoRetiredGeek on Error 4605 Command is not available
4 hours, Just nowRetiredGeek on Create Hyperlink in Column using VBA Code
4 hours, 9 minutes ago
Recent Topics
-
Patch Tuesday poll – how is the testing going?
1 minute ago
-
DPC WATCHDOG VIOLATION during upgrade
1 hour, 52 minutes ago
-
Create Hyperlink in Column using VBA Code
4 hours, 10 minutes ago
-
Computer suddenly shows in home network as media device
2 hours, 33 minutes ago
-
Windows 10 Insider build 19043.928 (21H1) released to Beta & RP
18 hours, 4 minutes ago
-
20H2 Printer Queue Icon now missing from Task Bar
27 minutes ago
-
Tips to protect a Laptop without battery?
12 minutes ago
-
April Patch Tuesday out – Exchange once again
2 hours, 18 minutes ago
-
Microsoft Account linking to X-Box ID
1 day, 4 hours ago
-
iOS : FCC Speed Test
22 hours, 55 minutes ago
-
Power crash when updating
1 day, 13 hours ago
-
USB 3.0 slows down by a factor of 10x when not used
1 day, 3 hours ago
-
Upgrade Firefox…recommendations please.
52 minutes ago
-
Two links the get to Outlook online?
1 day, 5 hours ago
-
Am I FLoCed? A New Site to Test Google’s Invasive Experiment
1 day, 22 hours ago
-
20H2 and NVMe SSDs
1 day, 5 hours ago
-
Why KB2999226 installed today?
1 day, 4 hours ago
-
Error 4605 Command is not available
4 hours ago
-
legitimate interest
2 days, 8 hours ago
-
How to customize and manage your Microsoft Account
1 day, 16 hours ago
-
New smartphone? Great! Now don’t charge it past 80%
1 hour, 57 minutes ago
-
Check or change Win10’s file-sharing encryption level
2 days, 12 hours ago
-
Freeware Spotlight — Killer
2 days, 12 hours ago
-
Known Issue Rollback
1 day, 16 hours ago
-
Dism RestoreHealth shows two “Versions” and Q re 20H2 “Experience”
2 days, 21 hours ago
-
Firefox SSD capacity usage ?
1 day, 23 hours ago
-
Android : New Wormable Malware Spreads by Creating WhatsApp Auto-Replies
3 days, 3 hours ago
-
KB4092436 – can neither install it or hide it
3 days, 1 hour ago
-
MS-DEFCON 2 – Deferring the April Updates
50 minutes ago
-
Tasks for the weekend – April 10, 2021 – change your Office
1 day, 2 hours ago
Search for Topics
Recent blog posts
- Patch Tuesday poll – how is the testing going?
- April Patch Tuesday out – Exchange once again
- How to customize and manage your Microsoft Account
- New smartphone? Great! Now don’t charge it past 80%
- Check or change Win10’s file-sharing encryption level
- Freeware Spotlight — Killer
- Known Issue Rollback
- MS-DEFCON 2 – Deferring the April Updates
Key Links
Copyright © 2004 – 2021 AskWoody Tech LLC. All rights reserved.