Windows 10: Question about origin and current copyright status of a microsoft product

Hello there everyone, I am here to seek out some information on this piece of audio that was used in some early windows 2000 builds. It is known simply as 'Windows NT Logon Sound' This is not the one that was shipped with NT4. But this is the one that was present in some betas with a so called 'NT 5.0'. This audio file has metadata crediting a Matthew A Felton 'title' Microsoft Windows NT 5.0 Logon Sound. Who appears to have worked for Microsoft at some point in time.I am running into some problems with a project I am working on. Sony is claiming that they own this audio track, and want to c

:)

 

Microsoft criticizes Google on copyright compliance

Microsoft, the corporation that has copyrighted the scroll wheel and double click, recently criticized Google for being too slack on enforcing copyright law. Microsoft claimed that Google "systematically violates copyright" law, citing Google book search and Youtube as examples.

Source: C|Net

 

Current Status of Windows 10 October 2018 Update version 1809

Update to current status of upgrade block in place on first page.

[table][tr][td]Date[/td] [td]Current Status[/td] [td]Affected Platforms[/td] [td]Details[/td] [/tr] [tr][td]December 1, 2018 5:20 PM PT[/td] [td]Upgrade block in place[/td] [td]

• Windows 10, version 1809

[/td] [td]Microsoft and Morphisec have identified an issue on devices that have installed Morphisec Protector or another application that uses the Morphisec Software Development Kit (SDK) including: Cisco AMP for Endpoints. These applications may impact customers’ ability to save Microsoft Office documents. Workaround: Uninstall affected applications and get updated versions from respective vendors when available. Next Steps: We are working with Morphisec and Cisco to address this issue in updated versions of their applications.[/td] [/tr] [/table]

 

Current Status of Windows 10 October 2018 Update version 1809

Update for "Current Status" of Windows 10 October Update on first page.

[table][tr][td]Date[/td] [td]Current Status[/td] [td]Affected Platforms[/td] [td]Details[/td] [/tr] [tr][td]November 28, 2018 5:00 PM PT[/td] [td]Known Issue[/td] [td]

• Windows 10, version 1809
• Windows Server 2019
• Windows Server, version 1809

[/td] [td]Mapped drives may fail to reconnect after starting and logging onto a Windows device. Symptoms include:

• In File Explorer, a red "X" appears on the mapped network drives.
• Mapped network drives show as "Unavailable" when you run the net usecommand from a command prompt.
• In the notification area, a notification displays, "Could not reconnect all network drives."

Workaround: See KB4471218 for workaround scripts to automatically reconnect a mapped network drive when you log on to the device. Next Steps: Microsoft is working on a resolution and estimates a solution will be available by early December 2018.[/td] [/tr] [/table]