From: Peabody on 13 Nov 2009 09:27 I finally installed the .NET 3.5 package through WU yesterday on my XP SP2 computer. And then it gave me other updates, including KB961118 which apprears to relate to printer drivers. After all this I have a new folder left called: E:\06b602b8cbd1353a0660e3d1084376 with subfolders amd64 and i386, each containing different versions of the same 7 files, including: ; MSXPSDRV.INF ; ; Microsoft system driver files for XPSDrv print drivers. Since all the files in this folder also now appear in C:\Windows\System32, it looks like the strange folder was just an intermediate location for installing the files, and could now be deleted (should have been deleted by WU). Could someone confirm that I can safely do that? Thanks.
From: Vincenzo Di Russo [MVP] on 13 Nov 2009 09:40 Peabody wrote: > I finally installed the .NET 3.5 package through WU yesterday on my > XP SP2 computer. And then it gave me other updates, including > KB961118 which apprears to relate to printer drivers. After all > this I have a new folder left called: > > E:\06b602b8cbd1353a0660e3d1084376 > > with subfolders amd64 and i386, each containing different versions > of the same 7 files, including: > > ; MSXPSDRV.INF > ; > ; Microsoft system driver files for XPSDrv print drivers. > > Since all the files in this folder also now appear in > C:\Windows\System32, it looks like the strange folder was just an > intermediate location for installing the files, and could now be > deleted (should have been deleted by WU). Could someone confirm > that I can safely do that? Thanks. http://support.microsoft.com/kb/951847/en-us "List of changes and fixed issues in the .NET Framework 3.5 Service Pack 1". Known issues -> see Issue 1 and Resolution. -- Vincenzo Di Russo Microsoft� MVP - Most Valuable Professional since 2003 Windows Internet Explorer, Windows Desktop Experience & Security My MVP Profile: https://mvp.support.microsoft.com/profile/Vincenzo My Blog: http://blogs.dotnethell.it/vincent/
|
Pages: 1 Prev: Windows Update can not display page - 8002802B Next: Error 0x8024D007 |