I can't remember, when I get on laptop later I will look, I know I not added it in as a selectable option yet. Just got back from a couple of nights in hospital , flare up of my condition due to cold air outside. Only walked to local shop too. Got in felt OK then a few minutes later I'm struggling to breathe and a painful chest, paramedics checked heart etc all ok. But they decided to take me hospital to be sure lungs not obstructed.
I found some pshell code to change long/short date which I found on my phone which I must of stored there ages ago. I think the format is for gb below. Code: Set-ItemProperty -Path "HKCU:\Control Panel\International" -Name sShortDate -Value "dd.MM.yyyy" Set-ItemProperty -Path "HKCU:\Control Panel\International" -name sLongDate -value "dd.MM.yyyy"
I think I not added in to mrp as it was awkward to get selectors right in the creator plus I not wanted to cause mistakes. It may have to be a manually added user's own tweak to match their locale etc.
I'm sure I have that registry tweak, will look in my archive of mrp stuff that I brought over to the replacement laptop.
Windows 11 24hx only as it for the new taskbar design not present in windows 10. Show full date: Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ShowShortenedDateTime"=dword:00000000 I believe that is the registry version: 0 = full date. 1 = abbreviated (default).
No idea if it can be set machine wide, such as if a new user is added later. EDIT: That can be achieved by adding to the ntuser.dat file.
Once I know the above registry tweak is confirmed working I will consider adding it in as a w11 tweak, that will be the last one to add for v159 of the project.
No problem, take your time. Health comes first. I hate it when MS makes such crippling choices just to save a few pixels of Taskbar real estate. Don't even oppose the feature itself (choices) but it being the default. /rant over
Exactly, it's change for changes sake. Probably keeps someone in a high paid job at m$! They must think the majority of users are using small screens something along the 10 inch/25cm size of a old ms surface type device.
Another taskbar/clock thing they backtracked on was the seconds on the clock. Their excuse was it uses more power, hmm ok, but it's a fraction of a watt at most. For many the seconds being shown is very useful.
Uploaded v159-BC3 for beta testers Added the new w11 option to expand the system clock's date instead of the abbreviated/shortened version. Not a policy edit. Updated the Creator (63c.0) with the above option on the w11 tab. The option can be used on any w11 (22xxx+) , it wont affect anything if the Build not have that within the kernel as it will just get ignored. Should also set for any new user added later.
Will resume work on finalising mrp v159 tomorrow evening. Been one of those hectic weeks, cleared old junk and loads of clothes damaged by the mould in my home. I have been ill for a couple of days after being in there for a few hours sorting and helping clear the stuff , the mould spores are still around and even the van man said he can smell the damp etc. Got several agencies behind me trying to get me moved to suitable accommodation but it's a long process and 'red tape' to go through, even though I have lots of proof of damage to home and my health. Pity the pen pushers don't go out to the places it might make them realise these hell holes exist!
Have uploaded v159_bc4 for beta testers. Nothing major, just a code update for two options. Remove/Hide Home and Remove/Hide Gallery from the navigation pane of File Explorer. Hopefully this will fix the issue where they sometimes came back after a Cumulative Update. It was reported to me that it happened more with win 11 Insider builds than the non insider builds, however the code m$ changed may get added at some point when they update the File Explorer app in the future.
I am hoping to Base Line v159 very very soon as its long overdue and quite a lot has been updated/added etc since v158 way back last year. I will try to get the change log sorted but there may be some items of what's changed etc due to the laptop failure i had, but the changes are in the code and if i can find the time to do a code compare i may be able to fill in any missing gaps. Because of all the issues i have had personally a lot has not been documented, sorry about that but at least MRP 159 will have some new things to play with
I have been given a Dell laptop (win 7 era and around 2014) to use for testing, i not tried it on win 11 yet but it works ok on w10 and once i get a ssd for it i can have something to test things i update/change before i beta release - as i not like to beta update before i can make sure the code is stable which has happened the past few weeks/months when i was unable to run test stuff myself first. The 500gb HDD is as expected slow, but it has a i7 4600 2.5ghz CPU, 8gb ddr3 ram and i think it has a 1080x900 screen, no fancy graphics, just the CPU's intel HD but for a freebie i not grumbling
As my main pc is in storage, i forgot to take a 2nd copy of the v2 of the GUI QT tool so i cannot continue with that at this time. My copy i thought was ok was no use and corrupted. However i do have the last test version of v1.02-xx so i can continue with that, it wont have the DPI aware code in but at least it still works. I will have to update the defender results as it can show that it is enabled when it is not, also the Tamper Protection status can be wrongly shown too. Possible cause is m$ changing something as usual to prevent fully disabling it? Once i get MRP 159 baselined then i can start working on the old GUI Tool to at least have something to upload to replace the version on Post #2 Any way for now i am going to watch tv and relax.