Looks Like Windows 24H2 broke Windows Remote Assistance. I can no longer connect to my users using MSRA.

[bswhipp]

Looks Like Windows 24H2 broke Windows Remote Assistance. I can no longer connect to my users using MSRA.

 

[ChatGPT]

It seems that the Windows 24H2 update has brought a plethora of issues, including problems with Windows Remote Assistance. A common problem encountered is the failure to obtain a proper IP address, leading to connectivity issues. Here are some possible steps to address the situation:

1. Static IP Assignment: Some users have found temporary relief by manually assigning static IP addresses. This method has mixed results, so it may or may not work for you.
2. Network Adapter Troubleshooting: Check if all your network adapters are enabled through the Device Manager, even if they appear disabled in the Control Panel.
3. Consider a Rollback: Although it's not guaranteed to resolve the issue, rolling back to the previous version (23H2) has helped some users restore connectivity.
4. Watch for Updates: Keep an eye on Microsoft's official support channels for any announcements regarding patches to resolve these issues.

These steps might help to alleviate some of the problems you're facing with MSRA after the Windows 24H2 update. If the problems persist, staying updated with Microsoft's fixes or community forums might provide further relief.

 

[bswhipp]

Wow. Microsoft really stepped in it with 24H2

 

[ChatGPT]

It seems that the Windows 11 24H2 update has indeed been a source of frustration for many users. Here are some key issues and insights related to the update:

1. Bugs and Instability: The update is filled with bugs, including performance issues, File Explorer crashes, Bluetooth connectivity problems, and visual glitches.
2. Remote Assistance Issues: Like you, other users have found Remote Assistance broken due to the update. There are widespread problems with network connectivity and obtaining a proper IP address.
3. Manual Fixes: Some users have attempted workarounds like manual installation of updates or using specific network setup changes, but these aren't guaranteed fixes.
4. Stay Updated/Cautious: Users are advised to monitor Microsoft's Known Issues page for any announcements regarding patches. Meanwhile, consider rolling back to a previous version if necessary.
5. Wait for Stability: If you haven't updated yet, it might be wise to wait until these issues are addressed and the update becomes more stable.

If you're experiencing these issues, keeping your system backed up and regularly checking for patches from Microsoft might help. Additionally, participating in community forums can provide further support and solutions as they emerge.

 

[bswhipp]

OK then what is this error for MSRA
DCOM got error "2147746132" from the computer Computer name when attempting to activate the server:
{833E4010-AFF7-4AC3-AAC2-9F24C1457BCE}

 

[ChatGPT]

The error code "2147746132" you're encountering in MSRA is related to DCOM (Distributed Component Object Model) permission issues. Specifically, it usually points to a lack of permissions for the COM Server application identified by a specific CLSID.

Steps to Resolve:​

1. Component Services Administrative Tool:
   • Press Windows Key + R and type dcomcnfg to open Component Services.
   • Navigate to Component Services > Computers > My Computer > DCOM Config.
   • Find the application with the CLSID 833E4010-AFF7-4AC3-AAC2-9F24C1457BCE.
   • Right-click on it and choose Properties.
   • Go to the Security tab.
   • Under Launch and Activation Permissions, click Edit.
   • Add the necessary user and provide the appropriate permissions, like Local Launch and Local Activation.
2. Review Permissions:
   • Check that the user account running MSRA has appropriate permissions for the specific CLSID.
3. Firewall/Antivirus Settings:
   • Ensure that no firewall or antivirus is blocking DCOM communications.
4. System File Checker:
   • Run sfc /scannow in an elevated Command Prompt to repair any system file issues.

These steps should help you resolve the DCOM error with the MSRA. If the problem persists, checking the Event Viewer for more detailed error logs can provide further insight.

 

[bswhipp]

CLSID 833E4010-AFF7-4AC3-AAC2-9F24C1457BCE is not there

 

[ChatGPT]

If the CLSID 833E4010-AFF7-4AC3-AAC2-9F24C1457BCE is not present, it's possible the registry entry might not be correctly set or is missing. Here are steps to help resolve DCOM-related errors:

Steps to Resolve DCOM Errors:​

1. Check Event Viewer:
   • Open Event Viewer (eventvwr.msc) and navigate to Windows Logs > System.
   • Look for any related DCOM errors and note any details, especially those involving permissions or missing entries.
2. Use Component Services:
   • Open Component Services (dcomcnfg).
   • Navigate to Component Services > Computers > My Computer > DCOM Config.
   • If the CLSID is not listed, it might be part of a removed or incomplete application.
3. Registry Check:
   • Open Registry Editor (regedit).
   • Navigate to HKEY_CLASSES_ROOT\CLSID\.
   • Ensure the CLSID folder exists. If it's missing, it might indicate an application's faulty installation or removal.
4. Reinstall Application:
   • If the missing CLSID pertains to a specific application, consider reinstalling the application to restore any missing components.
5. Check Permissions:
   • Use the Security tab in the properties of any relevant DCOM entry to ensure appropriate permissions are set.
6. Consult Logs:
   • Review Component Services logs and any associated logs from the application causing the error for further debugging information.

If these steps do not resolve the issue, consulting the details of the DCOM error in Event Viewer might provide additional context to diagnose the problem. If further help is needed, providing those specific Event Viewer logs might help narrow down the problem.

 

[bswhipp]

How do you reinstall msra?

 

[ChatGPT]

To reinstall Windows Remote Assistance (MSRA), you typically don't perform a standard installation process like other software since it's a built-in Windows feature. However, you can attempt to "repair" any issues with MSRA through several methods:

Steps to Repair MSRA​

1. System File Checker (SFC) and DISM:
   • Open Command Prompt as Administrator.
   • Run the following command to check for system file integrity:
     sfc /scannow
   • Next, run the Deployment Imaging Service and Management Tool (DISM) to restore health:
     dism /online /cleanup-image /restorehealth
   • These commands will check for and attempt to repair any missing or corrupted system files.
2. Windows Features:
   • Go to Control Panel > Programs > Turn Windows features on or off.
   • Look for features related to remote assistance or remote desktop and ensure they are enabled.
3. Perform a System Restore:
   • If none of the above steps work, consider using a system restore point to revert to a previous state where MSRA was functioning correctly.
   • Access this via Control Panel > System and Security > System > System Protection > System Restore.
4. Check Network and Firewall Settings:
   • Ensure your firewall settings permit MSRA to operate. This can be done in Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
   • Make sure Remote Assistance is enabled in System Properties > Remote settings.

These methods may help in fixing issues with MSRA by ensuring the related system files and settings are correctly configured.

 

[bswhipp]

I think Microsoft may have removed this feature without telling anyone in a recent update. It is not anywhere to be found.

 

[ChatGPT]

It appears that some updates have led to the removal or hiding of various Windows features, but there are no explicit mentions of Windows Remote Assistance (MSRA) being removed. However, updates sometimes inadvertently affect system features, causing them to appear missing or inactive.

Steps to Re-enable MSRA or Troubleshoot:​

1. Check Windows Features:
   • Go to Control Panel > Programs > Turn Windows features on or off.
   • Ensure that anything related to Remote Assistance or networking features is enabled.
2. Windows Update:
   • Sometimes updates can disrupt features. Make sure your Windows is up-to-date and see if any feature updates rectify the situation.
3. Feature Reinstallation:
   • Use the Command Prompt to ensure MSRA is available. Run msra to see if it launches.
   • If not found, attempting a repair installation via the Settings > Update & Security > Recovery might help.
4. DISM and System File Checker:
   • Run the following commands to restore system files:
     

     dism /online /cleanup-image /restorehealth
     sfc /scannow

5. Community Forums:
   • Consider checking Windows forums for similar user experiences. It might provide clues if this change was unintentional due to an update.

If further help is required, tracking updates on Microsoft's official websites or support forums might yield more specific solutions.

 

[bswhipp]

Like I said, looks like Microsoft removed it. See this link Quick Assist is the new way

Redirecting

 

[ChatGPT]

You're correct! Microsoft has been transitioning from Windows Remote Assistance (MSRA) to Quick Assist as the primary tool for remote support. Quick Assist is integrated into the Windows operating system and offers a streamlined experience for temporary remote assistance needs.

Key Differences Between Quick Assist and MSRA:​

1. Integration: Quick Assist is directly integrated with Windows 10 and 11 through the Microsoft Store, making it easy to access and update.
2. Functionality: Quick Assist is designed for straightforward temporary support, allowing users to quickly share screens and provide assistance over the internet. Unlike MSRA, it does not offer persistent remote access.
3. Usage Scenario: Quick Assist is particularly suited for ad-hoc support scenarios, like helping friends, family, or coworkers with immediate issues without setting up a persistent connection.

By using Quick Assist, Microsoft aims to provide a more modern, user-friendly solution for remote connectivity that fits current digital work trends.