@clio:
May I ask you to read <http://wiki.documentfoundation.org/BugReport>?

Then please:
- add information 
  -- concerning your PC
  -- details concerning unselected extensions (Name)
  -- How did you install: 
    --- your first LibO? 
      ---- Did you uninstall older OOo and / or LibO?
      ---- did you delete old user profiles?
    --- have those Extensions been installed for your older version(s)?
  -- everything else crossing your mind after you read a.m. URL

This problem occurs in Win XP SP2 with beta 2 or 3 (don't remember) and with Win XP (?) with RC1.
To reproduce:
1. Clean install, also delete the old profile before installing and the corresponding folder in Program Files if it is still there. When installing, choose "custom install"
2. Unselect Extensions component
Result: The bundled extensions installed anyway

Also, you can try to modify your installation, go to Add/Remove Programs, click "Change" button corresponding to LibreOffic. The extensions component is still unmarked.

See also http://nabble.documentfoundation.org/Non-removable-extensions-td1814379.html - This is also reproducible on Vista.

Tor, could you please have a look?

So we should remove the "extensions" in question from being visible in the installer, and the extension manager.

Haha, just teasing.

In RC1, the "Extensions" item in the installer does not have any subitems, its description does not say what functionality it actually contains, and it is also claimed to take zero disk space. (And, as this bug report says, even if one de-selects "Extensions", bundled extensions are still installed.)

I suggest we drop this item completely from the installer UI in 3.3, as it certainly is too late to start modifying the installer UI more fundamentally for 3.3 now and adding (back?) sub-items under "Extensions". Hopefully just dropping that non-informative and apparently pointless "Extensions" item is easy.

Additionally, I don't see the point in showing "extensions" that can't be removed, i.e. have the padlock image, in the Extension Manager at all. This just confuses users. Such things are then, in m humble opinion, not extensions.

Note that I said above this would be for 3.3.

For 3.4, I suggest that we move some of the bundled "extensions" to be normal features that are no more visible separately in the installer UI, or located in the installed file set, than any other functionality. Other bundled "extensions" could well be unbundled, if they truly are needed by just a small part of the user base.

Frankly, I find this whole idea that an arbitrary subset of features is marketed and packaged as "extensions" silly, and a historic relic from Sun days, presumably originally motivated by some non-technical reason.

Of course, the above is just my personal opinion, and not even a strong opinion. I don't care much anyway.

*** Bug 32388 has been marked as a duplicate of this bug. ***

Tor
Your comment#5 and observations are just the same as mine. 

+1

I think for 3.3 the best choice would be to fix the installer for Windows by adding subitems for different extensions, because this is the only way to uninstall bundled extensions.

Seems to be fixed in rc2
tested with:
1) LibO_3.3.0rc2_Win_x86_install_multi.exe+Win XP SP2
2) LibO_3.3.0rc2_Win_x86_all_lang.exe+Windows XP 64-bit sp2 ENU +MUI_RU

Closing due to Comment 9

@reporter:
Please feel free to reopen this Bug if you find out that the problem will have erappeared in a later LibO version!