There is a simple method to re-establish the trust relationship between the workstation and the domain controller. It only involves a single restart and a single step.
Open System Properties. This varies by Windows version. On Windows 10 and 11, open “Settings” select “System” and then open “About”. In Windows 10 select “Advanced system settings” on the right. In Windows 11 select “Domain or workgroup”. Both of them will give you a window that looks like this.
Select Change… and another window will pop up
Remove .local from the Domain: field
Click OK and it will welcome you to the domain.
Click OK on the welcome message
Click OK on the System Properties window. It will warn you that a restart is required so accept that to reboot the workstation.
Everything should be as before. If you open the window back up after the reboot, the .local domain name will again be in that field.
For the sake of data redundancy, I have copied this from Microsoft Support and claim no credit for any of this excellent documentation.
If some Windows functions aren’t working or Windows crashes, use the System File Checker to scan Windows and restore your files.
Though the steps below might look complicated at first glance, just follow them in order, step-by-step, and we’ll try to get you back on track.
Run the System File Checker tool (SFC.exe)
To do this, follow these steps:
Open an elevated command prompt. To do this, do the following as your appropriate:
If you are running Windows 10, Windows 8.1 or Windows 8, first run the inbox Deployment Image Servicing and Management (DISM) tool prior to running the System File Checker. (If you are running Windows 7 or Windows Vista, skip to Step 3.)
Type the following command, and then press Enter. It may take several minutes for the command operation to be completed.
DISM.exe /Online /Cleanup-image /Restorehealth
Important: When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
Note: Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.
At the command prompt, type the following command, and then press ENTER:
sfc /scannow
The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows.
Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished.
After the process is finished, you may receive one of the following messages:
Windows Resource Protection did not find any integrity violations. This means that you do not have any missing or corrupted system files.
Windows Resource Protection could not perform the requested operation. To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log. To view the detail information about the system file scan and restoration, go to How to view details of the System File Checker process.
How to view details of the System File Checker process
To view the details that are included in the CBS.Log file, you can copy the information to the Sfcdetails.txt file by using the Findstr command and then view the details in the Sfcdetails.txt. To do this, follow these steps:
Open an elevated command prompt as described in the previous step 1.
At the command prompt, type the following command, and then press ENTER:findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
Open the Sfcdetails.txt file from your desktop.
The Sfcdetails.txt file uses the following format:Date/Time SFC detail The following sample log file contains an entry for a file that could not be repaired: 2007-01-12 12:10:42, Info CSI 00000008 [SR] Cannot repair member file [l:34{17}]”Accessibility.dll” of Accessibility, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
How to manually replace a corrupted system file with a known good copy of the file
After you determine which system file was corrupted and could not be repaired through the detail information in the Sfcdetails.txt file, find where the corrupted file located, and then manually replace the corrupted file with a known good copy of the file. To do this, follow these steps:
Note You may be able to get a known good copy of the system file from another computer that is running the same version of Windows with your computer. You may perform a System File Checker process on that computer to make sure the system file that you intend to copy is a good copy.
Take administrative ownership of the corrupted system file. To do this, at an elevated command prompt, copy and then paste (or type) the following command, and then press ENTER:takeown /f Path_And_File_Name Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type takeown /f C:\windows\system32\jscript.dll.
Grant administrators full access to the corrupted system file. To do this, copy and paste (or type) the following command, and then press ENTER:icacls Path_And_File_Name /GRANT ADMINISTRATORS:F Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type icacls C:\windows\system32\jscript.dll /grant administrators:F.
Replace the corrupted system file with a known good copy of the file. To do this, copy and paste (or type) the following command, and then press ENTER: Copy Source_File Destination Note The Source_File placeholder represents the path and file name of the known good copy of the file on your computer, and the Destination placeholder represents the path and file name of the corrupted file. For example, type copy E:\temp\jscript.dll C:\windows\system32\jscript.dll.
If the steps above don’t work, you may need to reinstall Windows. For more info, see Windows 10 recovery options.
NOTE: As of Unifi OS v2.5.17 the podman command no longer works on UDM Pro devices. It may not work on any devices with the newer Unifi OS installed.
You can try this command to restart just the UniFi Network application.
systemctl restart unifi
Restart OS - To do this, SSH into device (see this article) and run
podman restart unifi-os
This will restart the UniFi Applications and Remote Management Service. Routing, VPN, and other network functions should continue to operate without any interruptions.
The web interface on the Unifi controller was no longer responding, and the CPU usage was way too high, so I knew I needed to restart something, but I could not take the main internet connection offline. Running this command fixed the immediate problem.
I just finished tussling with a client’s computer that was locked with a small legitimate program called Lock My PC from FSPro Labs. I found several articles talking about the response they had to an increase in the nefarious use of their program. Here is one of them at Bleeping Computer talking about the response fspro.net/lock-pc/ had for the scammers.
My customer had been scammed and had enough of dealing with them. The clowns threatened him with locking him out of his computer if he didn’t give them his banking login details. They were planning to make good on their threat with this program. It was very scary for him, but thankfully I was able to help him out of his pickle.
The recovery method offered on this page https://fspro.net/_service/lmpc-passrec/ did not work for me and after further digging, I realized that I was dealing with Lock My PC v4.6 and not with the latest v4.9.6. Ah ha! A clue!
The program is no longer offered by FSPro for download so I turned to Major Geeks for the newest version https://www.majorgeeks.com/files/details/lock_my_pc.html. After a boot into safe mode and an upgrade install of the program, the fix worked! Entering the code provided by FSPro revealed a recovery code that when entered into the online tool generated a passkey to unlock the program. The same passkey worked to unlock it at uninstall also.
A quick swipe with Revo Uninstaller later and everything is gone!
Kudos to FSPro for a decisive action to cut these crooks off at the knees.
My Logitech G502 was plaguing me with intermittent hitching. Sometimes it would work great for days and other times it would be barely usable. I assumed it was a driver or Windows issue. I tried many suggested solutions and none of them worked. The problem even pursued me through a major computer platform upgrade from Intel to AMD. The common denominator ended up being the mouse itself.
I installed Logitech G Hub and poked around until I discovered that I was able to edit the onboard settings of the mouse.
The Surface Tuning was set to custom. I changed it to default and it started behaving perfectly.
