Windows 10: I can't run Marvel Rivals, but I'm fully up to date?

For some reason, my computer won't run Marvel Rivals despite me updating my GPU to Intel® Arc™ & Iris® Xe Graphics. I have an integrated GPU in my laptop. I use a 12th Gen Intel® Core™ i7-1260P processor and my DirectX ver is DirectX 12. I meet all of the requirements?! My windows 11 is also ver. 24H2

:)

 

Outlook Out of date Settings

Hello Christine,

As the above description is not clear provide additional information to assist you better with this issue:

• Are you referring to Office Outlook (Mail client version)/ Mail app/ Windows Live Mail?
• What is the complete error message/ error code of this issue?
• What is the exact issues you are facing?
• What are the troubleshooting steps you have tried to resolve the issue?

If you are referring to Windows Mail app, let us try the below troubleshooting steps and check if it helps.

Step 1: I suggest you to check if there are any updates for Mail app in Windows Store. If found try to update the app.

Step 2: I suggest you to run Windows Store Apps Troubleshooter,
troubleshoots problems that may prevent Windows Store Apps from working correctly.

Refer: Run the troubleshooter for Windows apps

Step 3: I suggest you to check with the system Date, time and Time zone
is set correct.

Follow the steps to set the date and time:

• Type Date and Time in the search bar.
• Click Change date and time button.
• Click Apply and Ok to save the date and time.

Note: Click on the Time Zone tab to check the Time Zone.

Hope it helps. Reply to the post with the required information for further assistance.

Thank you.

 

Pentium M

Not sure what I'm looking at. Though when I do go to Options and then CPU it lists my CPU
as Intel Pentium M processor 1.73 GHz, and then under that it lists speed: 799.9 MHz
and then features and cache size.I ran the benchmark test and don't understand all
those numbers, but while testing I checked CPUZ and it still says it is running at 800 MHz.

 

marvell avastar wireless

Hi

I went through the items above including running DISM and sfc /scannow

Marvell AVASTAR Wireless still shows up with code 37.

Note 1: when searching, I've found references to the issue that occurred during the 14915 and people had to back out of the build. Here's the reference

https://twitter.com/cepowell/status/771082379049828352

Note 2: that my system started with a fresh install of Creators Update on fully formatted Surface 1 Pro (Marvell AVASTAR was working). After going to 16215, it stopped working