Jump to content

Windows 11 - Discussion


naiclub
 Share

187 posts in this topic

Recommended Posts

Yes, i do always disable other drives during windows install, to avoid creating a partition on one of them or stupid thing that windows installer can do, in contrary wise on macOS always perfect in terms of taking decision by itself, that don't break our feeling.
I think Microsoft need to cooperate with Apple to make windows more intuitive and perfect in many aspects, surely windows become from time to time near the macOS in some things, but clearly there's more work for Microsoft to do, and a lot if i'm not mistaking

Sent from my Phone using Tapatalk

  • Like 1
Link to comment
Share on other sites

Anyone provide me the link of latest Windows 11 Build 22000.65.iso 
I think anyone will have iso file using uupdump
Uupdump is my best way to get a clean trusted iso directly from the Microsoft servers and with the latest build update of course. Check out my earliest post with screenshots!

Sent from my Phone using Tapatalk

Link to comment
Share on other sites

Is the sleep working in windows 11? I have installed windows 10 in a NVME drive and Big sur in another nvme drive. If the sleep doesn't work in windows, it doesn't work in my hack also. I have to turn off hibernate mode in windows and also turn off wake on lan in the device manager to make sleep work in windows and after this I have no sleep issues with mac.

Link to comment
Share on other sites

On 7/5/2021 at 11:17 AM, naiclub said:

In this case, I talked to another person who asked recently. separate installation All unrelated drives must be closed. And leave only the drive that we will install, because otherwise the system will write the boot file together with the system boot drive that exists in the system immediately. what's worse If the drives are separated, the second boot will not boot.

Suggest moving the boot files from the hidden partition to the main windows partition.  Instructions on how to do this are on the web.

Link to comment
Share on other sites

  • 2 weeks later...
11 hours ago, eSaF said:

New update available for Windows 11 (10.0.22000.120)

 

Thanks @eSaF Hi @all

Sorry for OFF-TOPIC:

 

One of the BIOS features, is that keeps the current Date/Time/Year on an internal clock.  So, if the CMOS battery is dead, then your PC will lose the time. A this moment, I release that my Z390's Bios keeps always the same time: this morning is always Thursday,5 instead of Friday, 6. Can you confirm, it's a CMOS Battery issues (2 years old) or something else !

 

Please, let me know.

Link to comment
Share on other sites

3 hours ago, Matgen84 said:

 

Thanks @eSaF Hi @all

Sorry for OFF-TOPIC:

 

One of the BIOS features, is that keeps the current Date/Time/Year on an internal clock.  So, if the CMOS battery is dead, then your PC will lose the time. A this moment, I release that my Z390's Bios keeps always the same time: this morning is always Thursday,5 instead of Friday, 6. Can you confirm, it's a CMOS Battery issues (2 years old) or something else !

 

Please, let me know.

Hi - Try setting the Bios time again and see if the Time and Date remains constant but I suspect it is time to change the CMOS Battery as a few weeks ago I had to go through the same procedure because of the same problem you describe.

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, eSaF said:

Hi - Try setting the Bios time again and see if the Time and Date remains constant but I suspect it is time to change the CMOS Battery as a few weeks ago I had to go through the same procedure because of the same problem you describe.

 

Thanks @eSaF in the past, the battery is living during more than 3-5 years. This is the case for my Ivybridge config.
For my Z390 Aorus Master, I downgrade the Beta BIOS F11o to official BIOS F11n. If the BIOS clock not running, I will change the CMOS battery this week-end.

  • Like 1
Link to comment
Share on other sites

16 hours ago, Matgen84 said:

my Z390's Bios keeps always the same time: this morning is always Thursday,5 instead of Friday, 6. Can you confirm, it's a CMOS Battery issues (2 years old) or something else !

 

Please, let me know.

 

Check the timezone settings in Windows (maybe defaulting to USA)?

 

Time difference when dual booting between Windows and macOS can also be caused by the fact that Windows assumes the BIOS clock is set to local time while macOS assumes it is set to UTC.

 

Can use the RealTimeIsUniversal Windows Registry trick to synchronize.

  • Like 2
Link to comment
Share on other sites

5 hours ago, fusion71au said:

 

Check the timezone settings in Windows (maybe defaulting to USA)?

 

Time difference when dual booting between Windows and macOS can also be caused by the fact that Windows assumes the BIOS clock is set to local time while macOS assumes it is set to UTC.

 

Can use the RealTimeIsUniversal Windows Registry trick to synchronize.

 

Thanks @fusion71au I have to disk: Windows and macOS. For microsoft, I use regedit method to synchronize time between the two OS. In my case, the problem is elsewhere: the BIOS date/Time don't run at all (settings aren't resetting).
This is why, I downgrade the Beta BIOS F11o to official BIOS F11n. If the BIOS clock not running again, I will change the CMOS battery this week-end.

  • Like 1
Link to comment
Share on other sites

@Matgen84 - My Time problem came about as you described then I noticed the BIOS clock seconds was not flashing in the Time readout as normal, that indicated to me that the Battery was either spent or on it's way out. After I changed the Battery and reset the Bios Time, the seconds started to flash and that was the end of the Synchronised Time problem between Windows and OS X so I still think your problem points to the Battery if you've exhausted other probabilities. Good luck.

  • Thanks 1
Link to comment
Share on other sites

15 hours ago, eSaF said:

@Matgen84 - My Time problem came about as you described then I noticed the BIOS clock seconds was not flashing in the Time readout as normal, that indicated to me that the Battery was either spent or on it's way out. After I changed the Battery and reset the Bios Time, the seconds started to flash and that was the end of the Synchronised Time problem between Windows and OS X so I still think your problem points to the Battery if you've exhausted other probabilities. Good luck.

 

@eSaF - I have not the same behavior: the BIOS clocks remains stuck at the date / time of the previous motherboard start. I noticed that In Clover's debug.log. which always displayed the same date / time. It seems that the situation is normal since the return to the last official BIOS F11n for Z390 Aorus Master. My fingers crossed ... If this happens again, I will change the CMOS battery.

Link to comment
Share on other sites

 Share

×
×
  • Create New...