@danielraistrick Then everything works as intended. ITP (Infotainment theft protection) detects a module that doesn't belong to your VIN and shuts down the whole Infotainment.
You need to decode the CEM pin, IMMO pin and Security pin with vdash, and than you can disable ITP.
Or you visit a Volvo dealer and ask for the installation of software with the partnumber 31268617, which also disables ITP. But allot of dealers refuse to do this. Atleast here in germany.

I created a VMware VM with WIN11 25H2 to test this. Installation worked perfect, but i noticed 2 problems.
VIDAMonitor errors out at system boot with an error "Can't connect to database". Switching the start type of the SQL service from "Automatic (delayed start)" to "Automatic" solved this.
The desktop link to start Edge in IE Mode doesn't work. Had to manually enable IE Mode and add localhost/vida. Additionally i used this https://github.com/LesFerch/IEModeExpiryFix to make this permanent instead of just 30 days.

@aiveo https://youtu.be/JeP1lWSfAdA?is=YTg6CEC980bYtC5_ here is a video how to do it

@skalaev Than opt for BSR tuning or RICA.

@gintasd This basicly means the car is not ready for an emission test. DPF and cat to cold, EGR closed. Nothing to worry about. If you drive for 20-30 minutes and than connect vdash, everything should be green.

@joroartcorp this should restore the original factory software of the DIM, so correct milage and no DTC.

@ZaanTerror I did some testing with your newest version of VIDA. This time i created a Windows 2 Go-USB Stick with WIN11 25H2.
Clean Installation worked fine.
VIDAMonitor starts without errors.
IE Mode in Edge works without user interaction.

While playing with VIDA, I noticed 2 things.
When in parts catalogue, clicking on any position number in the parts diagram leads to a short freeze of Edge and the associated line in the parts list won't get highlighted.
The Software tab is completely empty/just shows a blank screen. As sw downloads don't work with this version of VIDA, and I look up sw numbers in Parts catalogue, this is no big deal for me. But still, is this intentional?
Both issues might be caused by the medium/low transfer speed of the USB stick I used, but I'm not sure. The overall performance feeling of your VIDA version is really good.

As an additional suggestion. Would it be possible to integrate the drivers for Mongoose and VXDiag adapters, as these quite often can be found inside the housings of DICEs bought from chinese plattforms?

@joroartcorp remappings/tunes for the ECM/TCM and changes in the CEM configuration are two completely different pairs of shoes when it comes to software updates with an official VIDA.
Mappings/tunes are only overwritten/deleted when a reload/update for the ECM/TCM is installed.
Changes in the CEM configuration get overwritten with the original configuration known to the volvo servers with every software update/reload that is performed with VIDA for any ecu in the car.
Normal diagnostics or activating service functions does nothing/keeps everything as is.
Additionally most tunes/remaps create a permanent checksum error, which tells the guys working with VIDA that the ECM/TCM was modified, so they won't perform updates/reloads without consent of the owners.
All the above is only valid for P1, P2, P3 cars. On SPA and newer any configuration change/tune is detected whenever VIDA gets connected and can lead to a blacklisting for software and OTA updates until the original software is present in the car.

@sangcXL3 I first stopped VIDA Monitor and all SQL services, then I uninstalled the old VIDA, everything related to SQL, and Isoview with their uninstallers. Rebooted the computer. And then I manually deleted all folders related to VIDA, Volvo, Isoview and Microsoft SQL. This is quite tricky as lots of those folders are hidden. Look into the subfolders of C:/ProgramData/ (hidden); C:/users/{yourWindowsusername}/AppData/ (hidden) press Windows-key together with R and then simply enter AppData and press Enter to open this folder; C:/Program Files (x86)/Common Files/; C:/Program Files/Common Files/. I also removed several registry keys in HKLM\SOFTWARE\ and HKLM\SOFTWARE\WOW6432Node.
After another reboot the new VIDA installed without problems.

The zig zag lines are a normal PWM signal. Not sure if the values are correct as I don't have access to an official VIDA subscription to check. But looks normal.

@Miki89 D5T5 doesn't let you see the pin. It is stored in the vdash database so you can use vdash. If you want to see the pin, you would need to decode your car with another another tool like p3tool, or you need to find someone who is able to retrieve the pin via the VIDA/Wireshark-method. But this will cost you money.

If you have a supported adapter, you could just connect your car to vdash, and simply click through the advanced configuration options, to see what is possible or not with your car. This way you can find out if Vdash is useful for you or not, before you spend money for nothing.

@Arnis2002 my current understanding is, that it's unclear if the car was remapped or not. If this is the case and the car was tampered by one of those wannabe tuners that think running crap like autotuner, which offers stolen software packages without checking if the software works or even matches the vehicle makes them a good tuner, then I agree with you. Return to 100% original software and then flashing a properly done remap based on that is the way to go. If this has to be done from one of the most expensive Volvo tuners around is another question.
The tunes offered by Vdash are made by Obbe-Tuning, and this guy also knows what he's doing, but for much less money.

@aiveo to code a new ignition key you first have to decode the IMMO pin. This should be the option, if my translator is correct. After that you can add new keys. The key wizard allows to just add the key without having to pair the remote part. Vdash should also show you how many keys and remotes are currently paired with your car.

"Engine service required" means there is one or more active error codes (DTCs) stored in the engine control module (ECM). You should see them after connecting Vdash and wait for all ecus to load. Best practice is to make a screenshot of all codes shown and clear them (ignition pos. II, ignition on, engine not running!). After that turn off the ignition for a moment, than start the car and rev around 1500 RPM for a moment, than read codes again and see what codes came back.

@ZaanTerror finally found the time to do some testing of your latest version (03.02.26 from MEGA).
Clean install worked flawless, as usual.
Playing a little on a 2001 S60 and a 2018 V60CC(P3) didn't bring up any problems. Diagnostics, parts catalogue and service functions were working as expected.
Good work!!!

Visit a volvo dealer and let them check for software updates. Most times it's caused by a combination of old/degraded batterie (new batteries can sometimes also be overmatured or degraded by wrong/to long storage) and a software bug. You can also try to charge your batterie with an AGM compatible charger (positive cable directly at the positive terminal of the batterie and negative cable to the chassis or engine). After it's fully charged, keep the car locked for at least 4 hours.

@Michel71 That`s a hard one to diagnose. Do you have any DTCs in the car? Is the Battery healthy (Idle voltage/ignition off + doors closed = lower than 12,5V = not okay)?
With your milage I wouldn't be surprised if the ignition switch is worn out, same for the fuel pump and ECM relais, as well as others. But I also wouldn't rely on the diagnosis of Xemodex. There are some reports of dying CEMs that were incorrectly said to be okay by them.
If want to check the electrics you can obtain the wiring diagrams for your car from here https://vidaresources.volvocars.biz/ewd/Eng/index.html the pin outs and signal descriptions can be found in VIDA under Information/product specifications/specifications electrical. If you don't have VIDA, ask the user ZaanTerror in this thread https://forum.d5t5.com/topic/249/vida-2014d-2015a-windows-11 for his version of VIDA. It's awesome and works flawless with Windows 10/11.

If you connect Vdash, do you see a software update for the TCM? Volvo has update the TCM software somewhere in the past to address problems such as yours. Rough shifting and different error codes related to it. No PINs needed for that.

Is the car tuned or stock?

Those codes are for too low shifting pressure, or slipping clutches in 2nd and 3rd gear and could be caused by the wrong oil, to low oil level or worn clutches or a worn torque converter.
When did those codes apear for the first time and under which circumstances?
What oil do you use? The correct oil from volvo has the part number 1161540/1161640 or Aisin JWS 3309.
Did you perform an adaption reset after changing all those parts?