Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Dutch	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: 07 Jul 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Finnish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: French	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update.
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Greek	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Hungarian	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Italian	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
This document also applies to Japanese (PC98). Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Korean	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Norwegian	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Pan-European	OS: 32-Bit Win	Release Date: N/A
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Polish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Portuguese (Brazil)	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Portuguese	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Russian	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Slovenian	OS: 32-Bit Win	Release Date: 07 Jul 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Spanish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Swedish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 Year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Thai	OS: 32-Bit Win	Release Date: 07 Jul 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 Software Update, Internet Explorer 5
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Product Details Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International Windows 95 shipped with various versions of Internet Explorer. It is recommended to be on Internet Explorer 5, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer that is installed. How the product handles dates: Storage. Dates are stored internally as 4-digit year dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit year date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit year date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues: WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". SHELL32.DLL - The "Find File" or "Folders Dialog" Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not return the proper date. To ensure proper handling of dates: set Regional Settings to 4-digit date handling, VDHCP.386 - Winipcfg/all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The show call log option doesn’t display date correctly after successful completion of telephone call. If date is adjusted to the year 2000, the date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 20th century (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant*
Language: Turkish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 software update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950	Category:Compliant#
Language: Vietnamese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
This document also applies to Vietnamese (enabled). To learn how to check your version of Windows 95, see KnowledgeBase article from Microsoft's Support site - Q158238. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this.   Product Issues: WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". SHELL32.DLL - The "Find File" or "Folders Dialog" Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not return the proper date. To ensure proper handling of dates: set Regional Settings to 4-digit date handling, VDHCP.386 - Winipcfg/all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The show call log option doesn’t display date correctly after successful completion of telephone call. If date is adjusted to the year 2000, the date will display as 100, 101, 102, etc. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 20th century (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the BIOS article in the whitepaper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950a	Category:Compliant*
Language: Arabic	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 Software Update, Internet Explorer 5.0
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
This information applies to Standard and Enabled editions. Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Product Details Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 5.0, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date.  TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: 4.00.950r-7	Category:Compliant*
Language: Hebrew	OS: 32-Bit Win	Release Date: N/A
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	Windows 95 year 2000 Software Update, Internet Explorer 5
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
This information applies to Standard and Enabled editions. Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Product Details Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 5.0, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date.  TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: Czech	OS: 32-Bit Win	Release Date: 07 Jul 1995
Operational Range:	-
Prerequisites:	Windows 95 year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: Danish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	-
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: Dutch	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	-
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: 07 Jul 1995
Operational Range:	-
Prerequisites:	Windows 95 year 2000 Software Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238. Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here. To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173. To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update. Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion. To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Windows 95	Version: OSR 1, 4.00.950	Category:Compliant*
Language: Finnish	OS: 32-Bit Win	Release Date: 30 Dec 1995
Operational Range:	-
Prerequisites:	Windows 95 Year 2000 Update
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	12 Nov 1999
Product Details
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238. Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update. To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International. Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows: January 1, 2000 would appear as 1/1/;1 February 3, 2023 would appear as 2/3/>3 March 5, 2036 would appear as 3/5/=6 COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029. XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.