Windows 10: fbl impressive code 10049 windows update

10045? Are you sure?

*sarc

 

Sorry my mistake i meant 10049.

 

Well, someone already have 11049. *Smile

 

Or 11094! *Smile

Lotsa typos in dese forums! *Eek

 

That's easy to fix. Blame it on auto-correct. *Smile

 

Will auto-correct take care of wrong build number? *Smile

 

50ME71M35, 5P3LLiN6 15 N07 7H3 0NLY PR0BL3M. *Smile

 

It is a known bug

Korea Media Player Center and Korea Messenger Center

 

I have reprinted my original post #28 above in order hopefully to get a straight answer and not be accused of creating an argument.

This thread is entitled fbl impressive code 10049 update so hopefully members will not regress what they did in the past with DOS, W98, XP, VISTA, W7, W8 and W8.1 and concern themselves with the present O/S, with particular emphasis on the first line of my original post as above.

As far as I can ascertain it is not possible to suggest changes to the registry in the Windows Insider Programme (see attachment)
If this is true this would reinforce my original statement, if not I stand to be corrected.

 

All you do is pick the topic your reg edit changes. If it changes how the start screen works you select Desktop and Start, etc.

 

I watched that screen for 40 minutes . That was after a 4 hour attempted update.

 

Exactly. I've got some sympathy for your original point - if you change something in registry (or just refuse to test some part of the OS because you don't like it) it will make it harder for Microsoft to gain useful information. This is a valid point. If you want make a thread here called "Should we test the OS as it is?" I would answer and to some extent agree with you as there are people who say "I'm not testing xyz because it doesn't work well enough for prime-time".

Your point that MS should have a section for registry changes unfortunately shows a lack of understanding of how Windows works or what the registry is. Anyone, any program, anything can write to the registry (within the limits of their authority and desire to stick to conventions).

Do you really MS they should have a team looking at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\{7746D80F-97E0-4E26-9543-26B41FC22F79} and see if some idiot programmer from France has added some key there?

And another team looking at HKEY_CURRENT_USER\SOFTWARE\MozillaPlugins\LWA64Plugin15.8\MimeTypes?

And these teams should somehow guess what app is involved?

In case you don't get it these questions are rhetorical.

If xyz app doesn't work you log it with the xyz app team to fix. By all means add more information and any workarounds you may have found.

Logging a case saying "set HKLM/{GUID}/random_key=4 stops windows freezing" will probably will not help any developers much if they are working on abc app and have no idea what you are talking about or even who the developers of xyz app are or what it is supposed to do.

 

That could come under keyboard malfunction. Blame it on the keyboard driver. *Smile

 

Sorry, what did I say?

 

not you! take it easy... *Smile he's quoting me. *Smile