{"id":11097,"date":"2019-09-10T00:09:57","date_gmt":"2019-09-09T22:09:57","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=11097"},"modified":"2019-09-10T00:11:04","modified_gmt":"2019-09-09T22:11:04","slug":"windows-10-version-1903-some-bugs-part-1","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/09\/10\/windows-10-version-1903-some-bugs-part-1\/","title":{"rendered":"Windows 10 Version 1903: Some bugs – Part 1"},"content":{"rendered":"

[German<\/a>]In Windows 10 May 2019 Update (V1903) there are some bugs that people have noticed. Here are some findings that blog reader Reto F. have pointed out to me. Nothing serious, but unsightly.<\/p>\n

<\/p>\n

\"\"Blog reader Felix R. already e-mailed me about this in mid-August 2019 and wrote the following: <\/p>\n

\n

In the appendix I described 4 bugs, which I stumbled across and can't find any further information on the net. I reported everything to Feedback.hub. But nobody was interested in this yet. Maybe you can make these bugs known to a wider audience. <\/p>\n<\/blockquote>\n

It's a well-known phenomenon, the Feedback-Hub is used to make people get rid of their displeasure – but it's not always corrected what was reported.<\/p>\n

#1: Time zone error [seems fixed]<\/h2>\n

Reto wrote: On Windows 10 1903 (also 1803) systeminfo.exe<\/em> returns a different time zone than the Settings page or the Control Panel. The same time offset but still wrong.<\/p>\n

\"Zeitzone(Zeitzone in den Einstellungen: Windows 10 V1903)<\/p>\n

\"Zeitzone
(Time zone in Windows 10 date dialog box)<\/p>\n

In the two screenshots above you can see the time zone setting of Windows 10 Version 1903 in the Settings app and in the Properties window Date and Time. The two settings are identical.<\/p>\n

\"Zeitzone
(Time zone of system info in Windows 10 V1903)<\/p>\n

On the other hand, if you query the system info in Windows 10 via systeminfo.exe<\/em>, it returns a slightly different value (Amsterdam is missing). The blog reader noticed this with the Windows 10 version 1903 Build 18362.175 and writes: With Windows 10 1703 this was still correct. I checked it at build 18362.329, so the information seems nor correct.     <\/p>\n

#2: Trustable websites not definable in IE settings<\/h2>\n

Internet Explorer has problems adding certain Web pages to the list of trusted Web pages. Reto writes that *.amazonaws.com<\/em> cannot be added to the trusted pages.<\/p>\n

\"Vertrauenswürdige<\/a>
(Click to zoom<\/a>)<\/p>\n

A strange error message. But it's even more crude – if you type an incorrect URL, it's assumed. The URL *.amazonaws1.com<\/em> can be added – I was able to verify that. <\/p>\n

\"Vertrauenswürdige<\/a>(Click to zoom<\/a>)<\/p>\n

Reto writes about it: A rogue, who thinks that the competition should be locked out. On Windows 8.1, both still work.<\/p>\n

#3: Data Execution Prevention Turns Off<\/h2>\n

In Windows, data execution prevention can be used to protect against viruses or malware. Windows 10 version 1903 has problems. Reto writes: <\/p>\n

\n

For security reasons I activate the data execution prevention since Windows XP for all programs. After each upgrade, the less secure default setting is active again.<\/p>\n<\/blockquote>\n

\"Datenausführungsverhinderung\"<\/p>\n

#4: Alt-D no longer works in German registry editor<\/h2>\n

In Windows 10 V1903  there is a localization error in the German registry editor. Reto writes about it:<\/p>\n

\n

Since the registry editor has an address line you can't call the file menu with ALT+D anymore. <\/p>\n

MS also uses ALT+D in the English version of the Explorer for the address bar. <\/p>\n

With the German version ALT+E is used in the Explorer to prevent the collision with ALT+D for the file menu. <\/p>\n

Unfortunately MS has not adapted this for the address line in Regedit.<\/p>\n<\/blockquote>\n

\"Registrierungseditor\"<\/p>\n

Not a drama, but also not really nice when the bugs are reported in the feedback hub, but nobody cares. In part 2 I pick up further inconsistencies.<\/p>\n

Similar articles:<\/strong>
Windows 10 V1903: Known Issues<\/a> \u2013 Part 1
Windows 10 V1903: Known Issues<\/a> \u2013 Part 2
Windows 10: Issues with update options \u2013 Part 1<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]In Windows 10 May 2019 Update (V1903) there are some bugs that people have noticed. Here are some findings that blog reader Reto F. have pointed out to me. Nothing serious, but unsightly.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[4,2094],"class_list":["post-11097","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-error","tag-windows-10-version-1903"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/11097","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=11097"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/11097\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=11097"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=11097"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=11097"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}