Printing word merger file restarts computer with blue screen

Q: Recently, some of our computers have this problem. Whenever they print a word merger document, it forces the computer restart with blue screen.

chicagotech.net: 1. Try to install latest printer driver.

2. If 1 doesn’t fix the problem, try to use Universal printer driver, in our case we change the Kyocera FS-4200DN KX to Kyocera Monochrome personal XPS Class driver.

Note: After we changed from Kyocera FS-4200DN KX to Kyocera Monochrome personal XPS Class driver, some email print has a problem. The way we do now is install the printer locally using IP address instead of ptinter server so that the user can switch the print driver by themselves.

RDP Problem caused program to stop working correctly

Situation: the client tries to access Windows 2008 R2 using RDP. He is able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE crashing. “A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.” Eventlog has the following: Log Name: Application Source: Application Error Date: 3/25/2015 2:50:21 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Description: Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7 Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315 Exception code: 0xc0000005 Fault offset: 0x000000000046d78c Faulting process id: 0x2164 Faulting application start time: 0x01d06734abf028a0 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\system32\mstscax.dll Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005 Faulting package full name: Faulting package-relative application ID:

chicahotech.net Resolution: 1. According to the error message, this problem caused by mstscax.dll which is Windows Remote Desktop Client relevant file. To fix this problem, you can try to use the command below to register this Dll file again for test.

Open CMD with administrator, Type the command below and press enter: regsvr32 %systemroot%\system32\mstscax.dll

After that, restart your computer to test this problem.

2. Try these 3 options: Option 1. Disabling Printer redirect on RDP connection resolved the crashing. Crashing was taking place on a Windows 10 PC using the native Desktop RDC. Option 2. Download the Microsoft Remote Desktop app from Windows 10 store. Option 3. Access our Remote7 instead of remote5 and remote6.  3. Or try this: Run the system file checker tool. Check the article http://support.microsoft.com/kb/929833 “How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7” 4. Allow Remote Desktop Via Windows Firewall. Especially, if the network is setup using public connection, make sure the Remote Desktop is allowed in Public firewall settings. Disable remote mapping or audio playback settings. In our case, When I clicked in the Remote audio playback settings I noticed Play on this computer was selected. Check Do bot play fix the problem. That fixed it! 5. if you repeatedly connect to the same computers that have the same desktop setups, the terminal service client will save a cached copy locally on your system so you don’t have to keep downloading it from the remote computer. It’s located here: %USERPROFILE%\AppData\Local\Microsoft\Terminal Server Client\Cache You could rename the .bmc files to .bmc.old and then retry your terminal services connection efforts. I believe the key to solving this issue specific to each case is looking in the event viewer. Look at not just the “Faulting application name” but also the “Faulting module name.” For me the faulting module was “dlxcrjdm.dll” which is an old Dell Printer Driver dll that I am guessing isn’t compatible with Windows 10 (which I just upgraded to). Anyway, after uninstalling the Dell printer, my problem was resolved. This type of approach may also solve the issue for those looking to use printers or audio as a local resource in the remote environment. To run event viewer, just hit the Start button and start typing in “Event Viewer.” You should be able to see in the “Summary of Administrative Events” any Errors (under “Event Type”) in the last hour and then find the one related to your issue. After you do find the “Faulting module name”, I suggest googling it to find out what it is and go from there. In our case, the client is running Windows 2008 R2 RD services. Their RDP client version is RDC 10.0.16299.15 (the latest build 2017.10.13). This version is not supported on Windows 2008 R2.

Cannot access other mailbox even we have assigned full permissions

Situation: User A needs to access user B’s mailbox. I have added the user A to user B’s Mailbox Delegation, but user A can’t access user B mailbox.

chicagotech.net resolution: Sometimes, you may have a problem to assign permission using Exchange admin center. In this case, you may want to use the powershell.

Now launch the Services Module from ‘Start’ > ‘Programs’ > ‘Windows Azure Active Directory Module for Windows Powershell’ , run as administrator. Then run the commands below to connect to Office 365

Set-ExecutionPolicy Unrestricted

$LiveCred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential

$LiveCred -Authentication Basic -AllowRedirection

Import-PSSession $Session

Connect-MsolService -Credential $LiveCred

To remove the permission run the following command:

Remove-MailboxPermission -Identity UserB@domain.com -User userA@domain.com -AccessRights FullAccess

NOTE : UserA@domain.com need to access userB@domain.com mailbox

To re-assign the permission: Add-MailboxPermission -Identity UserB@domain.com -User userA@domain.com -AccessRights FullAccess -inheritanceType All -Automapping $true

Fix Windows 10 freezes

Q: My windows 10 machine freezes for about 1 second when I right-click anywhere in desktop and also when I open up my browser. How do you fix it?

Chicagotech.net:

  1. This could be an issue with a system file being corrupt. Run the system file checker utility to fix it. Right click your start button and select Command prompt (Admin) to bring up elevated Command prompt. In Command prompt type sfc /scannow and press enter. Restart the computer.
  2. Run Deployment Image Servicing and Management. In the Administrator: Command Prompt window, type the following commands. Press Enter key after each command: DISM.exe /Online /Cleanup-image /Scanhealth 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.
  3. Check the Windows update status. It may have some updates waiting for installing.

Fix winretools low disk space

Q; My windows 10 keeps popup winretools low disk space warning. How can I turn it off or fix it?

Chicagotech.net: You may want to disable the waring by editing the registry. Here are how:

1. Open the Registry Editor by clicking on Start -> Run and running REGEDIT.

2. Navigate to the following location: HKEY_CURRENT_USER\Software\Microsoft\ Windows\CurrentVersion\Policies\Explorer

3. Right-click in the blank area of the right-hand pane of the Registry Editor and create a new DWORD Value by selecting New -> DWORD Value.

4. Name this new DWORD Value NoLowDiscSpaceChecks

5. Double-click on the new DWORD value and assign it a value of 1.

6. Close the Registry Editor and restart the computer.

Troubleshooting 0x0000001E (KMODE EXCEPTION NOT HANDLED) error

Q: After installing a windows 10 updates, I have a blue screen problem with this error: 0x0000001E (KMODE EXCEPTION NOT HANDLED).

Chicagotech.net: Here are some troubleshooting options:

  1. It could be Hardware problems. disconnect some hardware except keyboard, mouse and monitor. Or run safe mode.

2. Install the latest device drivers and firmware.

3. It could be corrupt system files issue. Use the System File Checker tool to repair missing or corrupted system fiels, for example: SFC /scannow

4. Check any recently installed software applications which might be incompatible with your Windows versions. You can run msconfig to disable tem for a test.

Can’t add second owner to Distribution in Office 365

Q: Before migrating to office 365, I can add second owner to a distribution in Exchange admin. But I can’t do it after we migrated our Exchange to office 365.

chicagotech.net: Assuming you still manage Active Directory on your site, you don’t have option to add group owner in AD and you will get an error if you try it on Office 365 Exchange admin center.

The only option I can think about is deleting the existing distribution group from your AD and then re-create it on Office 365. Then add second owner.

Windows error: 0xC1900200 – 0x20008 and 0xC1900202 – 0x20008

Q: My computer keep getting Windows 10 error messages; 0xC1900200 – 0x20008 and 0xC1900202 – 0x20008.

What could be the problem?

chicagotech.net: it could ne your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10. Double check the hareware reuirements.