DTS Wizard 2008 R2 ServicePack2+CU3 not work with some data types by Aruba.it

After installing CU3 for SQLServer 2008 R2 SP2 the Import export wizard fails with the following error while importing-exporting data from a SQL database, selecting "Query" as data source,
[Source Information]
Source Location : xxxx
Source Provider : SQLNCLI10
Table: [Query]
Column: VarcharField
Column Type: 200
SSIS Type: (Type unknown ...)
Mapping file (to SSIS type): C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML

The unknown data types are:

[varchar]
[nvarchar]
[text]
[ntext]
[varbinary]
[xml]
[image]

How to reproduce the bug:

1. Create table using the script below
Use [TEST]
GO
CREATE TABLE [dbo].[TestExport](
[VarcharField] [varchar](100) NULL,
[NvarcharField] [nvarchar](100) NULL,
[TextField] [text] NULL,
[NtextField] [ntext] NULL,
[VarBinaryField] [varbinary](50) NULL,
[XmlField] [xml] NULL,
[ImageField] [image] NULL
)
2. Right – click on Database TEST and select Tasks -> Export Data
3. On Data Source page select the SNAC 10 (the same behaviour is with the Microsoft OLEDB provider for SQL Server)and database TEST
4. On Destination page select SNAC 10 (the same behaviour is with the Microsoft OLEDB provider for SQL Server) and new/existent database
5. On Specify Table Copy or Query page select Write a Query to Specify the Data to Transfer and then write the query below and click Next and then Next again
Select * from Testexport
6. On reviewing Data Mapping page you will see the error:
Found 7 unknown column type conversion(s)
You are only allowed to save the package
7. If you select Copy data from one or more tables or view on the step 5 the data is exported without any issue.
8. The issue is NOT reproduced with the .NET Framework Data provider for SQL Server.

Additional informations:
- The file C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML is correct and contains the nodes for said data types;
- the problem is in the client, not in sql server engine: if i try the same export from the same database, using another client version, it works fine.