Symptoms
If a workstation is not attached to the domain or does not have Senso running, you can follow the procedure below to open Command Prompt.
Procedure
https://www.infopackets.com/news/9483/how-reset-any-password-windows-vista-7-8-10
Update
The new version will accommodate both 64-bit and 32-bit versions of Adobe Reader as some computers seem to have automatically updated to the 64-bit version. To update the existing GPO, follow the Procedure section below from step 2.
Symptoms
Windows 10 is setting default file associations to incorrect/problematic programs. The following GPO by default sets:
PDF files will open with Adobe Reader (and not Microsoft Edge as recently experienced).
HTML/HTM files will open with Google Chrome (not Microsoft Edge or Internet Explorer).
HTTP/HTTPS internet shortcuts and links within Office will open with Google Chrome (not Microsoft Edge or Internet Explorer).
MailTo links will open with Microsoft Outlook (not the Windows 10 Mail app).
Procedure
To set up SetUserFTA, download IIT - SetUserFTA. This is a GPO backup and requires the settings to be imported.
On K9Server > open Group Policy Management > right-click on Group Policy Objects > New > set the name to IIT SetUserFTA > OK.
Right-click IIT SetUserFTA > Import Settings > Next > Next > Browse > select the GPO - IIT SetUserFTA folder > OK > Next > Next > Next > Finish > OK.
Expand the Managed OU > right-click the Users OU > Link an existing GPO > select IIT SetUserFTA > OK.
Symptoms
During the install or upgrade of a third-party print driver, you may receive the following error message:
Windows cannot connect to the printer. No printers were found. (0x0000011b)
Procedure
On K9Server (or RM CC4 server):
Right-click Start Menu > Run > type regedit > OK.
Expand the navigation tree to the following - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
Right-click in the blank space on the right > New > DWORD (32-bit) Value > enter RpcAuthnLevelPrivacyEnabled > check that the value is 0x00000000 (0)
Restart the Print Spooler service.
Users will need to log off and on again to map the printers.
RM have released a tech article on the issue
https://support.rm.com/TechnicalArticle.asp?cref=TEC7785352&nav=0&referrer=SupportHome
Symptoms
Windows 10 computers suffer a BSOD with the error "APC_INDEX_MISMATCH" when printing.
Cause
Microsoft have acknowledged that the cumulative updates for Windows 10 released on 9 March 2021 can lead to this issue. The exact cause of the issue, be it the updates or certain printer drivers or printing apps, is still under investigation by Microsoft.
The affected updates are:
Windows 10 version 1803 - KB5000809 (OS Build 17134.2087)
Windows 10 version 1809 - KB5000822 (OS Build 17763.1817)
Windows 10 version 1909 - KB5000808 (OS Build 18363.1440)
Windows 10 version 2004 - KB5000802 (OS Build 19041.867)
Windows 10 version 20H2 - KB5000802 (OS Build 19042.867)
Procedure
If you are affected by this issue, you may wish to remove the update from your computers, though this will remove all of the other security and functionality fixes included in the patch.
Before you remove the update, you should follow the steps below to prevent them from reinstalling:
Open the RM Management Console (RMMC).
Expand Software, Windows Updates, Server Name.
Select Approved.
From the right-hand pane, right-click the update you want to decline and select Decline.
Repeat step 4 for any other updates you want to decline.
If the issue is only affecting a small subset of computers, you can manually remove the update by following the steps below:
Log on to a computer as a system administrator.
Open an elevated Command Prompt and run the command wusa /uninstall /KB:<patch number>.
Note: For example, to remove Windows 10 version 1909 - KB5000808, the command would be wusa /uninstall /KB:5000808.
If the issue affects a large number of computers, you can remove the update from all the computers by following the steps below:
Log on to the CC4 First server as a system administrator.
Open Windows Server Update Services.
In the left-hand pane, click your server name.
In the right-hand pane, click Search.
In the Search pane, ensure that Updates is selected. Enter the patch KB number and click Find Now.
Once the patch appears in the list, right-click it and select Approve.
In the Approve Updates window, from the All Computers drop-down menu, select 'Approved for Removal'.
Click the All Computers drop-down menu again and select 'Apply to Children'.
Click OK. The next time your computers check in with WSUS, the patch will be removed.
Symptoms
When performing a backup, the following error is displayed in Windows Server Backup: "Failed. Access is denied."
Cause
When attaching VHDs into Windows, the VHD needs to have granted the SYSTEM user modify permissions.
Procedure
Login to your Synology as an admin.
Open File Station > right-click on the Backups folder (or otherwise named) > select Properties.
Select the Permissions tab > select Create > type system and tick the SYSTEM user > in the Permission area, tick Read and Write > OK > OK.
Check
To check that the permissions have been applied correctly, attach the VHD in Disk Management; it should show the disk as Healthy (Primary Partition). Then, perform a backup; if data starts transferring then the correct permissions have been applied.
RM have released a tech article on the issue
https://support.rm.com/TechnicalArticle.asp?cref=TEC7785352&nav=0&referrer=SupportHome
Symptoms
Windows 10 computers suffer a BSOD with the error "APC_INDEX_MISMATCH" when printing.
Cause
Microsoft have acknowledged that the cumulative updates for Windows 10 released on 9 March 2021 can lead to this issue. The exact cause of the issue, be it the updates or certain printer drivers or printing apps, is still under investigation by Microsoft.
The affected updates are:
Windows 10 version 1803 - KB5000809 (OS Build 17134.2087)
Windows 10 version 1809 - KB5000822 (OS Build 17763.1817)
Windows 10 version 1909 - KB5000808 (OS Build 18363.1440)
Windows 10 version 2004 - KB5000802 (OS Build 19041.867)
Windows 10 version 20H2 - KB5000802 (OS Build 19042.867)
Procedure
If you are affected by this issue, you may wish to remove the update from your computers, though this will remove all of the other security and functionality fixes included in the patch.
Before you remove the update, you should follow the steps below to prevent them from reinstalling:
Open the RM Management Console (RMMC).
Expand Software, Windows Updates, Server Name.
Select Approved.
From the right-hand pane, right-click the update you want to decline and select Decline.
Repeat step 4 for any other updates you want to decline.
If the issue is only affecting a small subset of computers, you can manually remove the update by following the steps below:
Log on to a computer as a system administrator.
Open an elevated Command Prompt and run the command wusa /uninstall /KB:<patch number>.
Note: For example, to remove Windows 10 version 1909 - KB5000808, the command would be wusa /uninstall /KB:5000808.
If the issue affects a large number of computers, you can remove the update from all the computers by following the steps below:
Log on to the CC4 First server as a system administrator.
Open Windows Server Update Services.
In the left-hand pane, click your server name.
In the right-hand pane, click Search.
In the Search pane, ensure that Updates is selected. Enter the patch KB number and click Find Now.
Once the patch appears in the list, right-click it and select Approve.
In the Approve Updates window, from the All Computers drop-down menu, select 'Approved for Removal'.
Click the All Computers drop-down menu again and select 'Apply to Children'.
Click OK. The next time your computers check in with WSUS, the patch will be removed.
This can be triggered by the user accidentally setting the computer into Tablet Mode. To switch back to desktop mode:
Click the Notification icon on the far right of the taskbar.
At the bottom of the Notifications pane, select Tablet Mode so that it is not highlighted.
Symptoms can be experienced when navigating to File > Print in Word, or File > Save As resulting in an immediate crash. This mainly affects sites Ricoh printers and is caused by Windows Update KB4561608. The instructions below should be followed to fix the symptoms:
1. Logon to the server with the Windows Server Update Services (WSUS) role. On a K9 network, this will be K9Server-RDS. On a CC4 network this will be the First Server.
2. Navigate to Start > Windows Administrative Tools > Windows Server Update Services.
3. In the pane on the right, select Search > enter KB4561608 > select Find Now.
4. Right-click on each of the relevant versions of the update (normally just x64), and select Approve.
5. Select All Computers in the list and press Ctrl + R (approve for removal) > OK.
Source: https://serverfault.com/questions/1020879/print-spooler-crashing-after-kb4561608-with-ricoh-printers
Please be aware that there is an issue affecting a number of servers globally.
Symptoms:
Following a server restart, iSCSI disks do not reconnect. Disk Management shows the message "The disk is offline because of policy set by an administrator".
Procedure:
Open Command Prompt as an Administrator.
Type diskpart > press Enter.
Type san (which displays the current SAN policy on your computer. If there is an offline disk, it will display SAN Policy : Offline Shared)
Type san policy=OnlineAll (which will change your SAN policy to Online All. If succeeded, you will see the message “DiskPart successfully changed the SAN policy for the current operating system”.)
Source: https://www.partitionwizard.com/disk-recovery/disk-offline-because-policy-set-by-administrator.html
Please be aware that there is an issue affecting a number of servers globally.
Symptoms:
After installing the update and restarting, domain controllers will boot to the login screen. Whether the server is left here or logged onto, the server will initiate a restart.
Procedure:
If the update is pending installation
Do not install the update and wait until the February update.
If the update is pending restart after installation
It would be best to restart the server and complete the installation while on-site. This will prevent the need for an emergency visit when situated away from the school and allow you to observe if your server is affected. The installation can take around 30 minutes to complete (end user access to files will remain for most of this time). Once the installation has completed and the server has restarted, login as Administrator. If the server is logged out when you return, your server may well be affected.
If the update has installed and your server is frequently restarting
The following updates have been released by Microsoft to address the issue. This update only takes approximately 1-2 minutes.
Important: Please ensure you have good backups of the server that you are installing the update on.
Windows Server 2012 R2 - http://download.windowsupdate.com/c/msdownload/update/software/updt/2022/01/windows8.1-kb5010794-x64_3b350eb34833c9a3ac71d973db3fd8ae86a6b220.msu
Windows Server 2016 - http://download.windowsupdate.com/c/msdownload/update/software/updt/2022/01/windows10.0-kb5010790-x64_df441589ce8556dc94d051df30be306266b25828.msu
Windows Server 2019 - http://download.windowsupdate.com/d/msdownload/update/software/updt/2022/01/windows10.0-kb5010791-x64_466ad2172d2cc77b2125420c26b7f9ac00e197f4.msu
Windows Server 2022 - http://download.windowsupdate.com/d/msdownload/update/software/updt/2022/01/windows10.0-kb5010796-x64_ff1867cc8ed482b3115c6573e5743794c1dede8a.msu
To uninstall the update, the server should be restarted in safe mode.
Safe mode for Server 2012 / 2012 R2
Restart the VM > after the VMWare logo, keep pressing F8 until a boot menu appears - select Safe Mode.
Safe mode for Server 2016 / 2019
From Start > power icon > hold Shift + select restart > when the recovery menu appears select > Troubleshoot > Startup Settings > Restart. Then select Safe Mode from the list that appears during the next boot. Alternatively, boot from the Server ISO > set the language > Repair this computer > Troubleshoot > Startup Settings > Restart.
Login as Administrator (you may need to type the username as administrator@<domain>).
Start > Run > appwiz.cpl (Programs and Features).
Select View installed updates > locate the update(s) installed most recently.
Start > Run > type cmd > type wusa /uninstall /kb:500##### (where 500##### is the update number).
Restart the server.
This update has been officially been pulled by Microsoft, but to prevent the update from installing/uninstall the update via WSUS:
Login to K9Server-RDS as Domain Administrator.
Open Windows Server Update Services.
In the left-hand pane, click your server name.
In the right-hand pane, click Search.
In the Search pane, ensure that Updates is selected. Enter the patch KB number and click Find Now.
Server 2022 - KB5009555
Server 2019 - KB5009557
Server 2016 - KB5009546
Server 2012 R2 - KB5009624 / 5009595
Once the patch appears in the list, right-click it and select Approve.
In the Approve Updates window, from the All Computers drop-down menu, select 'Approved for Removal'.
Click the All Computers drop-down menu again and select 'Apply to Children'.
Click OK. The next time your computers check in with WSUS, the patch will be removed.
If the VM is hanging loading Windows before it gets to the logon screen, this will most likely be a service that's causing the issue. To enable safe mode on the server, perform the following:
Login to the ESXi web portal.
Check that the ISO has been uploaded for the server OS that you are fixing.
Mount the ISO to the VM and boot to it.
Select language > Troubleshooting > Command Prompt.
Enter the following commands:
bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /set {bootmgr} timeout 15
exit
Select Turn off you computer.
Start the VM > press F8 > select Safe Mode with Networking.
To allow for Windows function keys to be passed through to remote desktop sessions while using Senso, the settings within the application must be changed.
Open the Remote Desktop application or edit a Remote Desktop file.
Select the Local Resources tab.
Under Keyboard, select On this computer.
Following a restart of the server, Windows fails to boot with the above error code. This has been caused by a Windows Update corrupting the boot record. Follow the instructions below to resolve the issue.
1. On the affected server, boot to the Server 2008 R2 DVD.
2. Open the command prompt.
3. Enter the following commands:
bcdedit /export c:\bcdbackup
The operation completed successfully.
attrib c:\boot\bcd -h -r -s
ren c:\boot\bcd bcd.old
bootrec /rebuildbcd
Add installation to boot list? Yes<Y>/No<N>/All<A>:
Type Y and press Enter
BCDEDIT /set {default} nointegritychecks 1
c:
cd windows\system32\config
ren system system.old
cd regback
copy system c:\windows\system32\config
exit
Reference - Microsoft Answers - Total Identified Windows Installations 0
Reference - Microsoft Technet - Winload.exe Bootloop
Reference - Itomation - Windows Server Stuck on Microsoft Corporation Logo
Download the legacy version of Microsoft Remote Desktop here.