Go to your user TEMP folder:
Open a Windows file explorer and type %TEMP% in the breadcrumb bar, then hit ENTER.
Click the “Date Modified” column, so that the list is sorted by date.
Scroll down to where the files created on the day you installed SketchUp are grouped together.
Read the log files beginning with “dd_vcredist_” (I have three on my machine from my last install of SketchUp.) These log files are written by Microsoft’s Visual C++ Runtime installer.
SketchUp’s installer triggered a web install from Microsoft, for this because it needed the VC runtime libraries to be updated.
[quote=“SketchMan, post:7, topic:26176”]But it doesn’t explain why Sketchup needs to modify those files used by Bluetooth and PROSet.
…
Also because this is a fresh install of Sketchup it means this install is modifying pre-existing files probably used by other softwares or services - aka those are NOT files used only by Sketchup.
[/quote]
Partly true. But it is not SketchUp modifying anything. It is the Microsoft VC Runtime installer. Most every low level service is going to use the MSVC runtime libraries.
If you have concerns, take them to Microsoft. (They have forums where you can ask about the changes for the VC Runtime libraries. Perhaps someone has already asked the question, and an answer is waiting for you there.)
The SketchUp installer is NOT the only application installer in the world that can trigger an update from Microsoft for Dot NET or VC Runtime libraries. Repeat,… it is not unique to the SketchUp installer.
Lastly, you do not have to allow the updates to occur in the midst of the SketchUp install. I have in the past, elected to go to the Microsoft download site, and download the library installer(s) separately, and install them myself before running the SketchUp (or whatever application) installer.