Windows 10 22H2 can be rendered unbootable if ''Windows Fax and Scan'' is removed
There is a serious bug in the 32-bit kernel releases (x86) of Windows 10 22H2 (though older versions, such as 21H2 or 21H1 may also be affected; I have not tested). I was doing some test-installs of the latest 22H2 release, using install-media built from the Media Creation Tool. (The version that this tool creates is currently Build 19045.2006). To reproduce this bug, do the following: 1 Install the x86 version of Windows 10 Version 22H2 onto a PC, or inside a VM (e.g. Home or Pro) 2 After the Desktop appears, go to Start > Settings > Apps > Optional Features 3 Click "Windows Fax & Scan" in the list, then the "Uninstall" button 4 After the uninstall is finished, and "Reboot required" appears, restart the PC or VM session 5 During the next boot-up, it will first go to this screen briefly: "Updating your system 0%" But will then go to a blue-screen with this error: Stop code: KMODE_EXCEPTION_NOT_HANDLED What failed: NTFS.SYS 6 After a reboot, the blue-screen will appear again, then after the next reboot Windows will go to the "Preparing Automatic Repair" screen 7 The only way to repair the Windows install is to use a System Restore point, should one exist I have been able to replicate this issue on ALL x86 kernel installs of Windows 10 22H2 I have tested, but the 64-bit (x64, AMD64) kernel versions are unaffected. I have no ARM devices to test. Needless to say, this should be treated as critical as this is easily reproduceable, and uses only built-in options supplied with Windows, but leaves systems completely unbootable afterwards. Thanks
SBS 2011 Standard Fax Routing to Email Fails with “The following error occurred: 0x80040211”
First published on TechNet on Apr 11, 2011 [Today's post comes to us courtesy of Rod White and Shawn Sullivan from Commercial Technical Support]A while ago we wrote a blogpost regarding an issue where fax routing to email can fail on Windows Server 2008, upon which SBS 2008 is built.Considerations when Managing the SBS 2008 Fax Queue from Windows XP
First published on TechNet on Oct 23, 2009 [Today's post comes to us courtesy of Roderick White and Shawn Sullivan] By design, user accounts that do not belong to the Windows SBS Fax Administrators group are not able to manage the SBS 2008 Fax queue from the Windows XP Fax Console.SBS 2008 Fax Routing to Email Fails with "The following error occurred: 0x80040211"
First published on TechNet on May 28, 2009 [Today's post comes to us courtesy of Rod White]Customers are currently seeing issues where SBS 2008 servers receives faxes successfully, but intermittently faxes routed to email may fail.SBS 2008: Released to Manufacturing!
First published on TechNet on Aug 21, 2008 On behalf of the SBS team, I am extremely pleased to announce that Windows Small Business Server 2008 software has been finalized! Today both SBS Standard and Premium are being released to manufacturing, which means we begin the process of finalizing international versions, creating media, building packaging, delivering the product to distribution channels and handing it off to our OEM partners, so it will be widely available by our November 12 launch.Fax May Send the Wrong Attachment
First published on TechNet on Apr 07, 2008 [Today's post comes to us courtesy off Chris Puckett]If you use the fax functionality in SBS 2003 or Windows Server 2003 to fax documents or attachments, there is an issue where a document or attachment may end up being sent to the wrong destination.Incoming Faxes Can Take a Long Time to Route to SharePoint
First published on TechNet on Jun 05, 2007 [Today's post comes to us courtesy of Justin Crosby and Jim Martin]Customers who configure SBS fax to route to SharePoint and are heavy fax users may notice a delay in routing that gets progressively worse over time.
