RDCMan v3.21 crashing
Getting the following error System.NullReferenceException: Object reference not set to an instance of an object. at RDCMan.Nodes.Server.Dock() at RdcMan.ServerForm.OnClosed(EventArgs e) at System.Windows.Forms.Form.WmClose(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at RdcMan.RdcBaseForm.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, UInt32 msg, WPARAM wparam, LPARAM lparam) The error seems to happen when I have an undocked session, I restart the remote machine on the the undocked window, and it stays open, when I try to reconnect, on the same undocked window, it opens another docked session, I can login to the new session, and undock it, so now I have two undocked windows, the old one (disconnected) and the new one. I try to close the old one and I get the error shown below, (details above). If I click Continue, nothing happens, if I hit Quit, it closes RDCMan, as stated in the window.
August 2026 RDP font display glitch
In the last days, we have received two independent reports of font display problems in our MS Access based application. The symptoms are as follows: Some labels or text boxes are shown in a legacy system font instead of the font specified in the control (Segoe UI). Also, the label/text box is shown with a white background instead of transparent. Moving the Access window "fixes" the glitch. It happens at seemingly random places in our application at seemingly random times. Both reports have in common that the Access application is running inside an RDP session. In report 1, a work-from-home user used Remote Desktop to connect to their office Windows 11 PC, and, in report 2, a user executed the application on a Windows Terminal Server. Here are a few screenshots to illustrate the problem. The left side is the glitch, the right side is how it is supposed to look. The first row shows labels, the second row text boxes in a continuous subform. Report 1 is 16.0.20228.20186, 32 bit, M365 SAEC. Report 2 is 16.0.14334.20848, 32 bit, Office 2021 LTSC. Is this a known issue, or shall we continue to collect data about this glitch? Unfortunately, we haven't found a reliable way to reproduce it, so our ability to test it with different versions is limited.
Broken File History after July/August Updates (KB5101684 on Win11 25H2 / KB5120249 on Win10 22H2)
Hi everyone, I am writing to report a major regression bug with File History that was introduced in the recent Windows updates. This is happening across two entirely different machines with no settings changed, no system files modified, and no registry tweaks applied. The Issue: Windows 11 25H2 > after installing KB5101684 (July 29, 2026) Windows 10 22H2 > after installing KB5120249 (August 12, 2026) On both PCs backing up to a local drive (D:), the underlying files are actually being written to the drive, but the File History interface is completely broken: TheLast Backup time stamp in Control Panel frozen and fails to update automatically. In File Explorer, right-clicking new files > Properties> Previous Versions shows There are no previous versions available, making daily time-travel restoration impossible. Temporary Workaround: The only way to force it to sync is to go to Control Panel > File History > Select Drive, and re-select the D: drive again. This proves the backup engine works, but the automatic scheduling and catalog syncing are completely frozen by these updates. Please Help Upvote on Feedback Hub: I have already submitted this issue via the Feedback Hub but have received no official response yet. Since File History is critical for users who prefer local offline backups over OneDrive, we need to bring this to Microsoft’s attention immediately so they can patch it in the next cumulative update. If you are experiencing the same issue, please upvote my feedback link below:[Post your Feedback Hub sharing screenshot]How to submit support tickets?
Hi, folks. How does one submit a support request for the Exchange Online PowerShell v3 module? The following article instructs you what not to do, but provides zero detail on what to do: About the Exchange Online PowerShell V3 module | Microsoft Learn Similarly, the following articles highlight the "correct" process, however, it doesn't work: Get support - Microsoft 365 admin | Microsoft Learn How can I get support for M365 Exchange Online? - Microsoft Q&A Where having used the above option, you get to the end and are shown the following completely unrelated message with the support request having been lost in the process: The bug I'm trying to submit is outlined here: UShort Error with the Exchange Module - Microsoft Community Hub Cheers, LainRegression in v2605: Subform with overlapping controls breaks timer in unrelated form
I found another issue (sorry) which might be caused by the zoom-related changes in 2605. The following repro example works fine in 2604 (Monthly Enterprise Channel) but breaks in 2605 (Current Channel). Again, this issue is unrelated to zooming itself. Prepare database The repro requires three forms and a few controls. Since those are tedious to get right manually, I wrote some VBA code to do that for us. Execute BuildRepro() in the Immediate Window to create the forms and controls. Option Compare Database Option Explicit Public Sub BuildRepro() CreateFormASubform CreateFormA CreateFormB End Sub Private Sub CreateFormASubform() Dim frm As Form Dim ctl As Control Set frm = CreateForm() Set ctl = CreateControl(frm.Name, acTextBox, acDetail, , , 345, 1140, 1746, 260) ctl.TabStop = False Const textBoxTop = 260 Set ctl = CreateControl(frm.Name, acTextBox, acDetail, , , 56, textBoxTop, 270, 270) ctl.TabStop = False Set ctl = CreateControl(frm.Name, acImage, acDetail, , , 56, 0, 270, 270) Set ctl = CreateControl(frm.Name, acCommandButton, acDetail, , , 60, 795, 5895, 260) SaveAndClose frm, "FormA_Subform" End Sub Private Sub CreateFormA() Dim frm As Form Dim ctl As Control Set frm = CreateForm() Set ctl = CreateControl(frm.Name, acSubform, acDetail, , , 100, 100, 3000, 3000) ctl.SourceObject = "FormA_Subform" SaveAndClose frm, "FormA" End Sub Private Sub CreateFormB() Dim frm As Form Dim ctl As Control Set frm = CreateForm() frm.TimerInterval = 1 Set ctl = CreateControl(frm.Name, acLabel, acDetail, , , 100, 100, 5000, 1000) ctl.Name = "my_label" ctl.Caption = "Waiting for Timer..." frm.HasModule = True frm.Module.InsertText _ "Private Sub Form_Timer()" & vbCrLf & _ " Me.TimerInterval = 0" & vbCrLf & _ " Me.my_label.Caption = ""Done""" & vbCrLf & _ "End Sub" frm.OnTimer = "[Event Procedure]" SaveAndClose frm, "FormB" End Sub Private Sub SaveAndClose(ByVal frm As Form, ByVal newname As String) Dim oldname As String oldname = frm.Name DoCmd.Save acForm, oldname DoCmd.Close acForm, oldname DoCmd.Rename newname, acForm, oldname End Sub Run repro 1. Open FormA. 2. Open FormB (while FormA is still open). Expected result: FormB opens completely, the timer runs and the label reads "Done". Actual result: FormB opens "halfway" (it's visible, but it's tab is still missing, see screenshot below) and the label still shows "Waiting for Timer...". As soon as you right-click anywhere, the form finishes opening and the timer runs, changing the label to "Done". Notes: I tried to make the repro as simple as possible. If you remove one of the controls from FormA_Subform (or enable TabStops), the problem disappears. It might have something to do with overlapping controls: If you change textBoxTop from 260 to 280, so that it no longer overlaps with the image, the problem also disappears. We need the overlapping controls because in our real code the subform is continuous and displays data at different indentation levels (like a treeview).
Bug na bateria após atualização em 06/05/2026
Olá, pessoal. Tenho um notebook com processador Intel Core i5 de 11ª geração e faço parte do Programa Windows Insider. Na quarta-feira, 06/05/2026, por volta das 16h, ao desligar o notebook, apareceu a opção de atualização. Selecionei “Atualizar e desligar”. Aguardei o desligamento, fechei a tampa e deixei o equipamento conectado ao carregador, com aproximadamente 80% de bateria. Por volta das 18h, ao sair para dar aula, levei o notebook sem o carregador. Ao chegar à instituição e ligar o equipamento, ele permitiu apenas digitar a senha de login e desligou completamente, sem possibilidade de religar. Ao retornar para casa, conectei o carregador e o sistema indicava bateria em 0%. Aguardei cerca de 30 minutos, mas o nível de bateria não aumentou. Depois de alguns minutos conectado, consegui iniciar o notebook, porém a bateria continuava marcando 0%. Verifiquei o Windows Update e havia uma atualização não concluída. Tentei corrigir removendo a atualização e baixando novamente, mas ela não finalizava. Durante todo o dia 07/05/2026, tentei atualizar novamente, sem sucesso. O notebook ficou muito lento e a bateria continuava em 0%. Na sexta-feira pela manhã, 08/05/2026, após deixar o equipamento durante a madrugada baixando a atualização, ela chegou a 99%, mas não concluiu. Resolvi então restaurar o sistema, escolhendo a opção de manter aplicativos e arquivos. A restauração foi concluída com sucesso. O equipamento voltou ao normal em desempenho e, no primeiro reinício, a bateria voltou a aparecer com 100%. Realizei testes de carga e descarga durante a manhã de 08/05/2026 e utilizei o equipamento normalmente à tarde. Na manhã de 09/05/2026, notei algo estranho: a bateria ainda estava em 100%, mesmo após o notebook passar a noite hibernado. Continuei trabalhando e, de repente, o equipamento desligou sem qualquer aviso de bateria fraca. Ao conectar novamente o carregador e iniciar a máquina, a bateria voltou a ficar travada em 0%, mesmo após mais de 2 horas conectada. Ao verificar as atualizações, percebi que as mesmas atualizações estavam novamente disponíveis. Já removi a inscrição no Programa Windows Insider e desinstalei as atualizações recentes, mas isso não alterou a situação. Entrei em contato com o suporte da Microsoft e fui orientado a relatar o caso aqui, pois, por participar do Programa Insider, pode se tratar de um bug relacionado a alguma versão que esteja em conflito com o gerenciamento da bateria. Pretendo restaurar novamente a máquina para verificar se o funcionamento volta ao normal. As atualizações relacionadas são: * KB5073032 - 2025.11 * KB5082257 * KB5082417 Gostaria de saber se outros usuários do Programa Insider tiveram problema semelhante envolvendo atualização, bateria travada em 0% ou falha no gerenciamento de energia após atualização recente.
Graph /users query with mailboxSettings filters/expands excludes unlicensed users
Hello Microsoft Graph team, I would like to report what appears to be a bug in Microsoft Graph user queries involving mailboxSettings. Issue summary: When mailboxSettings is used in a filter or expand clause on /users, unlicensed users are not returned, even when they should match the filter. Example scenario: Filter used: mailboxSettings/userPurpose ne 'room' Observed behavior: Users without Exchange license/mailbox are excluded from results (or result set appears truncated to mailbox-enabled users). Expected behavior: All users should be considered in /users query evaluation. If a user has no mailbox settings, behavior should be consistent and documented (for example null handling), but those users should not be silently dropped from /users results unless explicitly filtered out by query semantics. Reproduction steps: In a tenant with mixed users: Licensed mailbox users Unlicensed users without mailbox Run a /users query that includes mailboxSettings in filter and/or expand. Compare returned users with a baseline /users query without mailboxSettings conditions. Notice unlicensed users disappear when mailboxSettings is involved. Sample request patterns: GET https://graph.microsoft.com/v1.0/users?$filter=mailboxSettings/userPurpose ne 'room' GET https://graph.microsoft.com/v1.0/users?$expand=mailboxSettings&$filter=mailboxSettings/userPurpose ne 'room'Urgent: Stuck KB5094126 (2026-06 Security Update) Loop on ASUS M413A
Hello, I have a very urgent issue. I am running an ASUS M413A Model M413IA-EB211T laptop running in the Windows 11 Insider Preview program. Right now, my machine is caught in a persistent and highly aggressive background update loop regarding the June 2026 Security Update KB5094126 for OS Build 26200.8655. The core background engines wuauserv and usosvc continually flip themselves back to Running and Manual/Automatic via background kernel self-healing routines. They are completely ignoring manual user flags to stay disabled via standard sc config commands. Because my system utilizes 8 GB of total RAM with shared integrated graphics, this ongoing background processing loop completely bottlenecks my remaining usable memory. This is throwing my processor usage to 100 percent and causing extreme, loud cooling fan strain whenever the AC charger is plugged in. Furthermore, the loop is continually eating 5 to 12 GBs of data at every single automatic download attempt, creating massive network usage and consuming massive storage bandwidth. My Exact System Specs: Device Name: LAPTOP-S4R984K2 Processor: AMD Ryzen 7 4700U with Radeon Graphics 2.00 GHz, 8 Cores Installed RAM: 8.00 GB 7.42 GB usable due to integrated hardware reservation Graphics Card: Integrated AMD Radeon Graphics 496 MB dedicated video cache System Type: 64-bit operating system, x64-based processor Storage Environment: 226 GB used out of 477 GB available total capacity What Actionable Steps I Am Seeking from the Community: Question 1. July Update Availability Check: Is there a way to safely skip this broken June patch and download the July updated version directly for my specific environment: Windows 11 Insider Preview Build 26200.8655? Question 2. Safe Standalone Roadmap: If I must install this, what is the exact method to download the correct standalone package for KB5094126 and initialize it manually without using the broken Windows Update pipeline? Question 3. Enforcement Command: What exact script can I deploy inside an elevated Administrator Command Prompt cmd or anywhere else to forcefully inject a registry block or anything else that stays active for as long as I put it? It must survive the aggressive Insider kernel health loops and hold the block long-term without risking database corruption or triggering automatic system overrides? Question 4. Cache and Datastore Maintenance Question: Is there any safe method to clear out the active transaction log database handles inside C:\Windows\SoftwareDistribution\DataStore\Logs? Could these lingering handles be the underlying reason why this build is failing to process the install, and how can they be purged without risking database corruption or a forced recovery loop? CRITICAL CONSTRAINT — Strict Risks I Must Avoid: I am completely refusing to do an In-Place Upgrade, a total system reset, or utilize the built-in Fix problems using Windows Update recovery utility. I need the forum experts to provide a path that completely guards against the following risks: Risk 1. System Freeze and Repair Loops: Falling into a mid-way installation freeze or an endless Automatic Repair boot loop where the machine fails to load back to the desktop. Risk 2. Display and Brightness Driver Corruption: Resetting, updating, or modifying my legacy display driver configuration. Any driver modification will immediately re-trigger unreadable thin system fonts, highly oversaturated display graphics, or high brightness spikes. Risk 3. Loss of Custom Profiles: Overriding my fine-tuned power slider behaviors, custom screen brightness thresholds, or my explicitly disabled auto-brightness/adaptive content feature tags. I must avoid resetting any of these features, as simply changing the brightness level itself causes a severe brightness spike. Complete Ledger of Troubleshooting Steps Taken So Far All Failed or Reversed: Step 1. Cache Purges: Cleared out the SoftwareDistribution Download folder, but the text entry remains stuck on the Settings app screen. Step 2. File-Level Permission Locks: Used icacls to deny the local SYSTEM account permission to execute wuaueng.dll. This successfully froze the loop for exactly 3 days until the automated 3-day Insider system health check forcefully restored factory permissions and restarted the services. Step 3. Firewall Barriers: Set up outbound Windows Defender Firewall block rules targeting the specific update services, which were actively bypassed by alternative network pipelines inside svchost.exe. Step 4. Service Configurations: Regularly deployed combination scripts to stop and disable wuauserv, usosvc, and bits via command line, which are immediately overwritten by the Insider kernel health loops. Step 5. System Health Restore and Scan Results: Ran standard administrative system repairs sfc /scannow and DISM /RestoreHealth. The tools reported that they successfully repaired something in the background, but the scan logs were completely unclear as to what was fixed, and it did not resolve the update loop. How can I safely acquire the standalone update package and force-install it without risking my current display profiles, causing a system freeze, or forcing an in-place operating system upgrade? Please let me know as soon as possible, I have been dealing with this for at least a month or longer.Search Bar not using colour theme on rest of device.
I restarted my computer today and this issue has suddenly occured, It doesnt matter what I change the colour theme too, when searching in the search menu I am presented with this light grey colour with white text which is incredibly hard to read, Online searches indicated stuff to do with Bing, Cortana and the Search registry keys, but I am not finding these keys anywhere in my registry to edit them. I have tried a few other solutions such as restarting the search services from task manager, but it is not applying the theme correctly. Had this computer for several years and never ran into this problem before, Any advice would be greatly appreciated.Pascal (10 series) GPUs on Windows 11 encounter artifacting boot loop when HDR is enabled in Windows
Bug: Users with Pascal (10 series) GPUs on the latest builds of Windows 11 are encountering an issue with an infinite boot loop that shows artifacting on screen when HDR is enabled in Windows 11. Workaround: Disable HDR in Windows 11 User reports: https://www.reddit.com/r/WindowsHelp/comments/1t5nt0u/hdr_blackscreen_artifacts_on_boot_after_recent/ https://www.reddit.com/r/pchelp/comments/1ngqsze/artifacting_and_crash_during_windows_boot_caused/ https://www.reddit.com/r/pcmasterrace/comments/1u5qfoo/is_my_gpu_doing_or_what/ Report this to NVIDIA: https://nvidia.custhelp.com/app/ask https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/587167/pascal-10-series-gpus-on-windows-11-encounter-arti/ Report this to Microsoft: https://www.reddit.com/r/Windows11/comments/1s0tt03/tip_of_the_week_if_you_want_to_quickly_share/
